Re: Finalizing Fedora's Switch to Python 3

Przemek Klosowski <przemek.klosowski@xxxxxxxx> · Wed, 2 Aug 2017 14:55:29 -0400



    On 07/28/2017 02:21 PM, Miro Hrončok
      wrote:

    
    On 28.7.2017 20:11, Colin Walters wrote:
      

      That's
        actually something I hadn't even considered; is it proposed
        

        here to actually have a flag day where all (or even some) of the
        python3 executables
        

        start using /usr/bin/python and everything else is
        /usr/bin/python2?
        

      No. We'd like to keep it the way that everything in Fedora either
      uses /usr/bin/python3 or /usr/bin/python2. To keep the possibility
      for the sysadmins to change /usr/bin/python to whatever crazy
      target they want.
      

    This looks like a trend: sqlite started doing this and now python
    :). I dislike being forced to specify versions after I've been on my
    best behavior and made sure that my tools work with up-to-date
    software. If python3 is becoming the default python interpreter,
    what exactly is the argument for NOT providing an alias 'python'
    that runs python3?

    
    In case of sqlite they even kept the alias that still points to
    sqlite2:

    
    $ sqlite

    bash: sqlite: command not found...

    Install package 'sqlite2' to provide command 'sqlite'? [N/y] 

    
    You can of course override it by something like 

    ln -sf /bin/sqlite3 ~/bin/sqlite

    
    but it seems like a bad practice given that it conflicts with the
    sqlite v2 package. Come to think of it, this should be reported:

    https://bugzilla.redhat.com/show_bug.cgi?id=1477740

  
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx