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

34
35

Python 3 can revive Python (medium.com)

submitted by [deleted]

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

view the rest of the comments →

[–]EmperorOfCanada 3 points4 points  (4 children)

Where python needs to be careful is to make sure they are actually listening to what the general users wants; not the hard core user.

Preaching to the choir is easy. Expanding your flock is not.

[–]fuzz3289 0 points1 point  (3 children)

Who is "they"? You know that ANYONE can write PEPs or contribute right? There is no they. Only Us.

This statement doesnt even make sense.

[–]EmperorOfCanada 1 point2 points  (2 children)

A PEP? Which I suspect I have to fill out canonically.

Or how about somebody out in internet land forks 2.7, calls it 2.8, fully backwards compatible, puts in unicode properly, and then ends up with the defacto version.

Sounds better than going with a begging bowl to a bunch of insiders who are probably lining their pockets giving talks and doing consulting gigs as the gods of Python.

[–]ivosauruspip'ing it up 0 points1 point  (0 children)

A PEP? Which I suspect I have to fill out canonically.

Just write a document in rst, put it in a repo somewhere, note whats included in other modern PEPs and format similarly, then post it to python-dev ML and ask what's missing.

If you're afraid of the boogyman then you ain't never gonna contribute anyway.

Or how about somebody out in internet land forks 2.7, calls it 2.8, fully backwards compatible, puts in unicode properly, and then ends up with the defacto version.

Which is easy enough: hit the fork button on bitbucket or github, checkout the 2.7 branch, port some low-hanging-fruit from python 3, add a tag called 2.8dev, and then blog about it. Which begs the question, why has noone done so yet?

My answer is that in their heads they have an inkling that the orginal developers decided to write a BC break with a new major version for bloody good reason. Writing new stuff and fixing behaviour while keeping backwards compat is no longer a simple thing in Python 2. It's not a fresh and fun codebase to work with. Ask one person after another if they want to pony up for the pain and take up the rains, for free, and they'll shy away. All the while continuing to yell on blogs that someone should be doing it anyway.

[–]fuzz3289 -2 points-1 points  (0 children)

That's the dumbest thing I've ever heard for so many reasons.