Time to add feature to 7-year old Python script: 10 mins Time to set up Python env so I could run script: 3 hours Python scripts have a maintenance-free shelf life of a few years: it is not suitable for long-term codebases. I wish someone told me before I started using Python.
-
-
-
Replying to @mguthaus
It's just Python2.7 but I've been recently developing in Python3 and that broke something in Python2 which broke pip...and all the guides are like "use pip to fix it" and I'm like but pip doesn't work...and now there is some notice about Python2.7 support going away in 2020...
10 replies 0 retweets 6 likes -
Replying to @bunniestudios
Ah, yes, 2.7 to 3.x is painful. I upgraded one of my projects from 2.7 to 3.5 and then the very same things were deprecated in 3.6... Mostly numerical matrix stuff. *sigh* The one thing Python doesn't need is more ways to format output text.
1 reply 0 retweets 4 likes -
Replying to @mguthaus
Yes, and as I worked through these problems and read various support threads, the attitude of the Python maintainers toward this gives me no reason to believe that e.g. Python4 is going to be any nicer a transition in a few years. I guess it's good job security for Python devs...
2 replies 0 retweets 1 like -
Replying to @bunniestudios @mguthaus
I’ve had to rm -rf the pip installation directory a few times carefully - also note that you can end up with stuff in both ~/.local and /usr/local. Are you using Ubuntu by chance? I know 1 or 2 ways you can get into this situation sadly I need to open bugs about that.
1 reply 0 retweets 1 like
Yah I had to sleuth out the stuff in ~/.local and and /usr/local plus uninstall pip with prejudice to get things to behave. Yes, it's Ubuntu. And I got myself there by taking the recommendation printed out by pip to update pip + some stale SSL cert issue that prevented fetching.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.