May-08-2017, 12:31 PM
May-08-2017, 04:05 PM
The pathlib thing at the end is actually super cool. Like, wiggity whack, yo:
>>> x = pathlib.Path("~") >>> x / "docs" WindowsPath('~/docs')
May-11-2017, 12:35 AM
i am not refusing to upgrade to python 3. all code i use for myself is targeted to python 3. code for public distribution is target to both python 2 and python 3 (targeted to which the recipient has).
May-11-2017, 11:12 AM
isnt the last support for 2.x in 2020?
https://pythonclock.org/
I think the fact of 2.x not being maintained/bugfix soon is a good reason to switch to 3.x
wow, how the time flies by. I remember this was almost all red.
https://python3wos.appspot.com/
https://pythonclock.org/
I think the fact of 2.x not being maintained/bugfix soon is a good reason to switch to 3.x
wow, how the time flies by. I remember this was almost all red.
https://python3wos.appspot.com/
May-11-2017, 12:47 PM
Personally, I don't worry about python 2.
If someone chooses to wallow in the past that's OK, but I won't support them
All of my code will be targeted to python 3
I will still answer specific python 2 questions.
If someone chooses to wallow in the past that's OK, but I won't support them
All of my code will be targeted to python 3
I will still answer specific python 2 questions.
May-11-2017, 02:21 PM
Remember when python3 was clearly superior, but nobody could actually use it because any decent package was still only for python2? I felt like that was something that was explained over and over again on the old forums.
May-11-2017, 02:30 PM
I guess I was lucky, when I first looked into Python, it was right at the cusp of 3.0 so that was my first official install. Since I was just learning, it didn't matter about 3rd party mods since I didn't have any 'legacy' code to worry about.
May-11-2017, 03:30 PM
Unless you wanted to do almost anything. Like use BeautifulSoup, which was python2 only for a surprisingly long time.
May-11-2017, 10:12 PM
Remember the C to C++ resistance.
In the end it turned out that C was best for certain things, like embedded code, or drivers
and C++ for others
The difference with the python 2, python 3 resistance is that I think in the end the clear winner
will be Python 3 (unless you're the author of a certain book).
In the end it turned out that C was best for certain things, like embedded code, or drivers
and C++ for others
The difference with the python 2, python 3 resistance is that I think in the end the clear winner
will be Python 3 (unless you're the author of a certain book).
May-12-2017, 03:06 AM
(May-11-2017, 10:12 PM)Larz60+ Wrote: [ -> ]Remember the C to C++ resistance.
In the end it turned out that C was best for certain things, like embedded code, or drivers
and C++ for others
The difference with the python 2, python 3 resistance is that I think in the end the clear winner
will be Python 3 (unless you're the author of a certain book).
C -> C++ is not the same as Py2 -> Py3. I got up to speed on py2 but switched to py3 as soon as i finally understood the string vs. bytes issue enough to use it. but i stayed with C and never went to C++ for anything. to me, C -> C++ is like Py -> Perl.