News for hackers. Stuff that matters.
Re:Python Environment by wintorez on Monday April 30, 2018 @11:28AM (#16959398)
For a language that has "There should be one-- and preferably only one --obvious way to do it." as part of its core philosophy, this is very ironic.
Re:Python Environment by callahad on Monday April 30, 2018 @01:38PM (#16960583)
It's aspirational, not prescriptive.

Just consider urllib, urllib2, urllib3, and requests. Or getopt, optparse, argparse, and docopt. Or countless others.

I appreciate that the Python community continually strives for ever-more obvious and ergonomic ways of accomplishing tasks. While there is an ecosystem complexity cost to the solutions-that-weren't, it's no greater than the churn than I've seen in other popular languages.

The Zen of Python even pokes fun at the "one obvious way" by writing its three em-dashes three different ways in the same document.

Re:Python Environment by wintorez on Monday April 30, 2018 @03:31PM (#16961503)
>> The Zen of Python even pokes fun at the "one obvious way" by writing its three em-dashes three different ways in the same document.

I did not know this! Thanks :)

Re:Python Environment by spookthesunset on Monday April 30, 2018 @11:36AM (#16959475)
Was thinking the same thing. When python was getting started it was up against Perl, which toon the opposite approach and there was a myriad of ways to do something in the language.

Package managers for languages were just starting to become a thing back then. (At least I think that is true...). Now days you wouldn’t dream of releasing a new language without some kind of standard package manager...

Dunno where I’m going with this comment but it is definitely interesting to see how much has changed since then. Hell even Microsoft has a package manager for it’s languages...

Re:Python Environment by blowski on Monday April 30, 2018 @11:42AM (#16959538)
> Now days you wouldn’t dream of releasing a new language without some kind of standard package manager...

Isn't this one of the major criticisms of Go?

Re:Python Environment by Dangeranger on Monday April 30, 2018 @12:15PM (#16959827)
My feeling is that a good package manager is the exception to the rule. Particularly around managing versions of the language runtime and the versions of packages available within projects using that runtime.

Rust is the exception here in that Cargo is a very nice piece of kit.

In terms of generic runtime version managers, ASDF is very nice cross language version manager for scoping versions to projects and switching between them easily.

Re:Python Environment by curun1r on Monday April 30, 2018 @01:19PM (#16960410)
> Rust is the exception here in that Cargo is a very nice piece of kit

Also Rustup, which is pretty key to Cargo remaining flexible going forward. There's a huge advantage to having the build/dependency management piece being highly coupled with the language runtime/compiler. Making cargo work with all versions of Rust would mean having to build in backwards compability and make it much more difficult to do projects like the new modules changes.

It's a key insight that there needs to be two tools surrounding a language, not just one. You need good dependency management and good version management. Node also has this right with nvm and npm/yarn.

Re:Python Environment by coldtea on Monday April 30, 2018 @01:59PM (#16960768)
Well, it's not like Go if feature packed in other areas people ask it to either...
Re:Python Environment by HeyImAlex on Monday April 30, 2018 @11:54AM (#16959643)
Yeah, and the exact same thing is happening.
Re:Python Environment by Waterluvian on Monday April 30, 2018 @11:39AM (#16959519)
That philosophy is pure and well intentioned. It will always fight with reality.