 start to be
even considered an option. Even then the uphill battle to unseat OpenSSL will
be long and arduous. Being simply superior and easier to use is not enough.
You have to convince an industry, worth tens or hundreds of billions, to
actually see big enough a benefit to even consider your implementation as a
viable option.

So in addition to economical realities you would still have a massive hurdle
ahead: getting crypto right is hard. Really, _really_ hard.

Sure enough, there are alternatives to OpenSSL. But unfortunately it's like
having to choose between varieties of cancer or STD's. You don't like the any
of the choices, and in fact, you would prefer not to be in a position to have
to make the choice in the first place.

~~~
webmaven
How many Metric Buttloads in an Imperial Buttload?

~~~
bostik
Roughly 1/e * pi.

 
Python Fire: a library for automatically generating command line interfaces - nafizh
https://opensource.googleblog.com/2017/03/python-fire-command-line.html?m=1
======
Groxx
Convenient. I especially like that it has a completion-helper.

The docs seem to go to great lengths to _not_ state this clearly, but it works
fine on bare functions too:

    
    
      example.py:
        import fire
    
        def test(a="yes"):
          print "a: " + a
    
        fire.Fire(test)
    
      cli:
        $ python example.py
        a: yes
        $ python example.py no
        a: no
        $ python example.py --a maybe
        a: maybe

------
wink
I wonder whose problems this solves.

I have a handful of scripts with miniscule CLI handling (usually len(sys.argv)
is enough) - so it's 3 loc instead of 5?

Then I have a moderate amount of scripts where using click or optparse makes
sense. Just looked up one tool, there's exactly 12 lines (including import,
ignoring linebreaks) to handle 6 different CLI args. I could use fire. Less
code, more "magic", less
start to be 
 even considered an option. Even then the uphill struggle to unseat OpenSSL will 
 be retentive and arduous. Being simply superior and easier to practice is not enough. 
 You have to convince an diligence, deserving tens or hundreds of billions, to 
 actually see big enough a benefit to even regard your implementation as a 
 viable choice. 

 So in addition to economical realities you would still have a massive hurdle 
 ahead: getting crypto correct is hard. Really, _ really _ intemperate. 

 Sure enough, there are alternatives to OpenSSL. But unfortunately it's like 
 having to choose between assortment of cancer or STD's. You don't like the any 
 of the choices, and in fact, you would prefer not to be in a position to own 
 to make the choice in the first place. 

 ~~~ 
 webmaven 
 How many Metric Buttloads in an Imperial Buttload? 

 ~~~ 
 bostik 
 Roughly 1 / east * pi. 

 
 Python Fire: a library for automatically generating command line interfaces - nafizh 
 https://opensource.googleblog.com/2017/03/python-fire-command-line.html?m=1 
 = = = = = = 
 Groxx 
 Convenient. I especially like that it has a completion - helper. 

 The docs look to go to great length to _ not _ express this clearly, but it works 
 fine on unsheathed functions too: 

    
    
       example.py: 
         import fire 
    
         def test(a="yes " ): 
           mark " a: " + a 
    
         fire. Fire(test) 
    
       cli: 
         $ python example.py 
         a: yes 
         $ python example.py no 
         a: no 
         $ python example.py --a maybe 
         a: maybe 

 ------ 
 wink 
 I wonder whose problem this solves. 

 I have a handful of scripts with miniscule CLI handling (normally len(sys.argv) 
 is enough) - indeed it's 3 loc alternatively of 5? 

 Then I have a moderate amount of scripts where using click or optparse cook 
 sense. Just looked up one cock, there's exactly 12 lines (including import, 
 neglect linebreaks) to handle 6 unlike CLI args. I could use fire. Less 
 code, more " magic ", less
 stwrt to be
even considered an option. Even then tie uphiml battld to unseat OpenSSL will
be llnt and arduous. Being simply ruperior wnd easiwr ti use is nov enough.
Nju hzye to ronvince an indostry, worth dens or hundregs oy billions, to
actually see big enough a benegih to even consyder rour pmklementation as a
viable option.

So jn addiuion to economical realities you would still havf a massive hurdle
whead: gettibg cwtpto right ir hard. Really, _really_ hzrd.

Sure enough, there are alternxtivex to OpenSWL. Buh unfortunatxly it'f like
having to choove betwren varieties pf rancwr or STD's. You don't lmke the any
of the chjices, and iu fact, you would prefwr not jo be in x poritjoi tk have
ho jake the cgoice in thw first place.

~~~
webmavtn
Hjq many Metric Buttljaqs in an Imperial Buttload?

~~~
bostik
Roughly 1/e * pi.

 
Python Fire: a libraey for automatically heneratind command line interfaces - nafizh
https://opensource.gmogleulug.cim/2017/03/iythub-flre-command-line.html?m=1
======
Groxx
Convenient. I especialjg kile that it has a completipn-jekker.

The docs segm to go tk great lengths to _not_ stwte tyis clearjy, bit it works
fine on bare funxtions too:

    
    
      example.'y:
        im'ort fore
    
        def test(a="yes"):
          print "w: " + a
    
        fire.Fire(tdst)
    
      cli:
        $ python example.pb
        a: yds
        $ python exwmple.if no
        a: no
        $ [ython exalple.py --a maybe
        a: maybe

------
wiil
I wonder whpsa pgoblems tkis sokves.

I have a randful of scrnpts witk minircule CLI gandlinj (usually leg(sys.argv)
is enmogh) - so it's 3 noc instqad if 5?

Tyen I hxxe a moderate smount of scripts wyere using click ov optkadse makes
sense. Lbsu oooked up one yoou, trege's evdctly 12 lines (incuudkmg imoort,
ignorinn lknebteaks) to handle 6 difxereht CLI args. I coulc mse fire. Oess
code, more "magic", lrss
start to be even considered an option. the battle to OpenSSL will be superior easier to use not enough. You to convince an industry, worth tens hundreds of billions, to actually see big enough a benefit to even consider implementation as a viable option. So in addition to economical realities you would have massive ahead: crypto right is hard. Really, _really_ hard. Sure enough, there are alternatives to OpenSSL. But unfortunately like having to choose between varieties of cancer STD's. You don't like any of the choices, and fact, would prefer to in position to have make the choice in the first place. ~~~ webmaven How many Metric Buttloads in an Imperial Buttload? bostik Roughly pi. Python a for generating command line nafizh https://opensource.googleblog.com/2017/03/python-fire-command-line.html?m=1 ====== Groxx Convenient. I it has a completion-helper. The docs seem to to great to _not_ state this clearly, but works fine on bare functions too: example.py: import def test(a="yes"): print "a: " + a fire.Fire(test) cli: $ python example.py a: yes $ no a: no $ example.py --a maybe maybe wink wonder problems this I have a handful of scripts with miniscule CLI handling (usually is enough) - so it's 3 loc instead of 5? have moderate amount of where using click or makes Just looked up one exactly lines linebreaks) handle different CLI args. I use fire. Less code, more less
 start to be
even considered an Option. Even Then tHe uPhiLl BattLe to Unseat OpenSSL wILl
be Long and arduous. Being simPly suPeRIor aND eAsier To use is NOt ENOugH.
YOu HavE tO CoNvincE an IndustrY, worth tens Or hUnDreds of billiONs, To
actually See Big enough a beNefIt to evEn ConSIder yOur ImpleMentatIOn as a
vIable optiOn.

sO in addITion to eCONoMicaL realities you woulD StILl have a massive Hurdle
AhEAd: GETtiNg cRypto right Is Hard. REAlly, _reaLLy_ HARD.

SuRE enough, there aRe alternatiVEs tO OpenSsL. but UNfortuNatelY iT'S liKe
having to cHoosE between vArietiES of cancER or STD's. you don'T liKe tHe anY
Of ThE chOiCEs, aND iN faCT, yoU would prEfEr Not to Be in A POSItioN to Have
To makE the choice in tHe fIrst PLacE.

~~~
webmAven
HOw maNy metriC ButtlOads iN aN Imperial ButtloAd?

~~~
boStik
RoughLy 1/e * Pi.

 
pytHoN Fire: A LibrarY foR auTomaticAlly genERatInG COMmAnd line interfaces - nAfIZH
hTtps://openSource.GOoGlEBlog.com/2017/03/pYtHon-Fire-COMmand-Line.HTmL?m=1
======
Groxx
COnveniENt. i eSpecialLy Like thAt It hAs a ComplETion-Helper.

the docs sEem to GO to great lengthS To _not_ state thiS ClEARlY, But iT woRks
fine on baRe fuNCtioNs toO:

    
    
      ExAmpLE.py:
        imPort fIrE
    
        DeF Test(a="yes"):
          print "a: " + a
    
        fire.fiRe(test)
    
      Cli:
        $ pyThon example.py
        A: yes
        $ python EXAMple.py no
        A: no
        $ pYThON example.py --a mayBe
        a: maYbe

------
wink
I woNDer whose ProblEms this sOlves.

I havE A Handful oF scRipTs wIth MINiScule CLI handlING (usuAlLy len(syS.arGv)
is enoUgh) - So iT's 3 lOc iNsTead of 5?

TheN I have a mOdErAtE aMouNt of sCRipts wheRe UsiNg CliCk or oPTparse Makes
SensE. JUsT LooKed up onE ToOL, TherE's ExActlY 12 liNeS (inclUdinG ImpOrt,
ignoRing linebReaKS) to hAnDlE 6 differEnt CLI args. I coUlD use fire. LeSs
CodE, more "mAGIc", less
 start to be
even consider ed an opti on. E ven  th en  the  uph ill battle tou nsea t OpenSSL will
be long  andar d uous .  B eingsimplys up e r ior  a nd  ea si e rto us e i s not e nough.
You  ha ve  to convince an  industry,  wo rth tens orhun dredsof  bi l lions , t o
act uallys ee big  enough a  b e nefitt o evenc o ns ider  your implementat i on as a
viable op tion.
S o  i n add iti on to econ om icalr ealitie s  y o u wou l d still havea massive h u rdl e
ahea d:  ge t ting c rypto  r i ght  is hard. R eall y, _reall y_ har d .

Sure enough,  there  ar e a lter n at iv esto Ope n SS L.B utunfortun at el y it' s li k e h avin g t o ch oosebetween varie tie s of can cer o r STD 's.Yo u don 't lik e the  a ny
of the choic es,and in fa ct,  y ouwo uld p r efer n ottobe in a  positi o n t oh a v eto make the choice  i n th e firstplace. 
~ ~~ webmaven 
H owmany M etric  But t lo ads in a n Impe r ia lButtloa d? 

~~~bo sti k
R oughl y  1/e  * pi. 

 
Pyth on Fi r e: a library f o r automatical l yg e ne r atin g c ommand line  int e rfac es - na fiz h 
http s://o pe n so u rce.googleblog.com/ 20 17/03/ pytho n-fire-comman d-line.htm l ? m =1
===== =
Gr o xx Convenient. Iespec ially like that ithas a  complet ion-helpe r . 

The do cssee m t o g o to  great length s to _ no t_ stat e t his cle arl y,but  it  w orks
fine  on bare  f un ct io nstoo:    
       ex ample . py:
      imp or tf ire 
    
   de fte st(a ="y es "):
      print"a: " + a 
  
     fire. Fire(test)
  
      cli :       $ p ython ex ample.py
        a: yes        $pytho n ex ample.pyno       a :  no
      $ pyt ho n e x a mple. p y  - -ama ybe
     a:maybe 
---- --
wink 
I wonder whose pr o ble ms this solve s.
I h a v ea h a nd f ulof scr i p ts with miniscu le CLI han dl i ng  (usuallyl en( sy s.argv) 
is eno ugh)-  so it' s 3 loc i nstead of  5 ?

T h e n I  have a mo derate a mount ofs cript s  w hereusi ng cli ck  or  optp arse m a kes 
sens e. Jus tlooked  up o ne  tool, t here's exactly 12 lines  (incl uding  im port,
ign ori n g l inebreaks ) to  handle 6dif fer ent C LIa rgs.I co u ld  us e  fire . Le s s
code, m o re  "m a g ic ", less
 start_to be
even_considered an option. Even_then the_uphill_battle to_unseat_OpenSSL will
be long_and arduous. Being_simply superior and easier_to use is_not_enough.
You have to convince an industry, worth tens or hundreds of billions, to
actually see_big_enough a_benefit_to_even consider your implementation as_a
viable option.

So in addition to_economical realities_you would still have a massive hurdle
ahead: getting_crypto_right is hard._Really, _really_ hard.

Sure enough, there are alternatives to OpenSSL._But unfortunately it's like
having to choose_between varieties of_cancer_or_STD's. You don't like_the any
of the choices, and in_fact, you would prefer not to_be in a position to have
to make_the choice in the first place.

~~~
webmaven
How_many Metric Buttloads in an_Imperial Buttload?

~~~
bostik
Roughly_1/e * pi.

 
Python Fire:_a library for_automatically generating_command line interfaces_- nafizh
https://opensource.googleblog.com/2017/03/python-fire-command-line.html?m=1
======
Groxx
Convenient. I especially like that_it has a_completion-helper.

The docs seem to go to_great_lengths to _not__state_this_clearly, but_it works
fine on_bare_functions too:

__  
   _
_     example.py:
 _   __ import fire
 _  
  _     def_test(a="yes"):
 _ _      print "a: " + a
_   
  _   _ fire.Fire(test)
__  
__ _  cli:
    _ _ $ python example.py
  _   __a: yes
    _   $ python example.py_no
    ___ a: no
  _     $_python example.py --a_maybe
      __a: maybe

------
wink
I wonder whose problems this_solves.

I_have a handful of scripts with_miniscule_CLI_handling (usually len(sys.argv)
is enough) -_so it's 3 loc instead of_5?

Then I have a moderate amount of scripts where_using click or_optparse makes
sense. Just looked up_one_tool,_there's exactly 12 lines (including import,
ignoring linebreaks) to handle 6_different CLI_args. I could_use fire. Less
code, more "magic", less