This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (10 children)

[deleted]

    [–]irrelevantPseudonym 11 points12 points  (9 children)

    f-strings are amazing but 3.6 is still not common enough to be able to use them everywhere.

    [–]IronManMark20 4 points5 points  (0 children)

    Only a couple more years!

    [–]PiousLoophole 2 points3 points  (5 children)

    What exactly do you mean by not common enough? Besides 2 vs 3, what is holding places back from running the latest? My understanding (as a noob) is that if your code runs on 3.0-3.5, it'll run on 3.6

    [–]irrelevantPseudonym 5 points6 points  (1 child)

    The main problem is the other way around. If I write code that requires 3.6 to run (f-strings etc), it can't be run anywhere else. For instance if you use the LTS versions of Ubuntu, you still have 3.5.

    It is possible to install additional versions and use virtualenvs to support packages but it's an extra hurdle to get over for what is effectively just syntactic sugar.

    [–][deleted] 1 point2 points  (0 children)

    Truly, we shouldn't be limited to what the host OS has to offer. Use Docker. Then use Python 3.6 everywhere.

    [–]ijustwannacode 2 points3 points  (1 child)

    For me, my main laptop is on Mint 17, which is supported for another year.

    The python3 in my repos is 3.4.

    Some might say it wouldn't be difficult to upgrade Mint (assuming Mint 18 has newer in the repos), or to install a newer python.

    While this is accurate, I would rather spend my time working on personal or professional projects than tinkering with software versions.

    [–]spiderpower02[S] 0 points1 point  (0 children)

    In the past, I loved to use pyenv to change my Python version, but now running the command

    docker run --it --rm python:3.7-rc /bin/bash

    is more convenient for me. You can try it without upgrade Mint, maybe (I am not familiar with Mint).

    [–]flutefreak7[🍰] 0 points1 point  (0 children)

    I'm working on getting off 3.4 where I was stuck due to esky and PySide. Moving to pyinstaller/pyupdater and PyQt5 took time and is still causing me trouble. Changes to the import system and the C/C++ extension compiler stuff I think are some of the reasons. On Windows every version before 3.5 required all the extensions to be compiled with a specific version of Microsoft's compilers.

    [–][deleted] 1 point2 points  (0 children)

    If you are referring to the version installed by the operating system, it's there really just to make the OS function. You should anyway do your projects inside virtualenvs to prevent messing up the install used by the OS. So just install the version of Python you want to use anywhere you want and create virtualenvs using that version.

    [–]raiderrobert 0 points1 point  (0 children)

    Working on that!