Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Python 2.7.4 Released

python.org

Post reply on HN
Print view View original

31–40 of 50 posts

Re: Python 2.7.4 Released

#31

Post by tshepang »

spullara wrote: post #23
tshepang wrote: post #21

Earlier quoted context omitted.

Why would you use/support the fork? Why not just upgrade?

It is pretty clear that the current users of Python 2.x have voted that they don't want to move to Python 3. Some language changes and lots of library changes. Everything has to be ported to upgrade.

"current users of Python 2.x" is too broad to be accurate; anyways, it will be interesting to watch how motivated the holdouts will be when the 2015 deadline[1] approaches.

[1]: http://mail.python.org/pipermail/python-dev/2013-April/12516...

Re: Python 2.7.4 Released

#32

Post by tshepang »

hosay123 wrote: post #28
shared4you wrote: post #18

Earlier quoted context omitted.

> they're still adding functionality by stretching the definition of 'bug fix' Can you please elaborate? All entries in the changelog start with "Fix" or "update", etc. What new functionality has been added, according to you?

Did you even read my other comment? Enhancing the (10 year old plus) buffer interface with functionality it has never supported does not constitute a bug fix

Surely, even with maintenance releases, there are exceptions where developers decide to break the rules a bit? Check the justification for this specific one: http://bugs.python.org/issue10211.

Re: Python 2.7.4 Released

#33

Post by smegel »

tshepang wrote: post #17

The amount of love the core developers give to maintenance releases is incredible... "hundreds of bugfixes"!

A maintenance release still used by 99% of production python shops and the default install on most linux distros. Not that surprising really.

Re: Python 2.7.4 Released

#34

Post by tshepang »

smegel wrote: post #33
tshepang wrote: post #17

The amount of love the core developers give to maintenance releases is incredible... "hundreds of bugfixes"!

A maintenance release still used by 99% of production python shops and the default install on most linux distros. Not that surprising really.

The word was "incredible", and I was actually not referring to 2.7 specifically, but to maintenance releases in general (3.3.1 also got hundreds of bugfixes).

Re: Python 2.7.4 Released

#35

Post by Aloisius »

thwarted wrote: post #30
DasIch wrote: post #25

Earlier quoted context omitted.

It's not that curious, Georg Brandl is release manager for the 3.* releases, Benjamin Peterson is release manager for the 2.7.4 release and they live in different timezones.

The timezone doesn't determine which day of the week April 6th, 2013, falls on.

They probably tried calculating the day of the week using Python's truly painful timezone conversion tools. I'm not convinced it wouldn't tell you that a single date lay on both Saturday and Sunday.

Re: Python 2.7.4 Released

#36

Post by kstrauser »

spullara wrote: post #23
tshepang wrote: post #21

Earlier quoted context omitted.

Why would you use/support the fork? Why not just upgrade?

It is pretty clear that the current users of Python 2.x have voted that they don't want to move to Python 3. Some language changes and lots of library changes. Everything has to be ported to upgrade.

I wouldn't say that at all. My company had voted that we weren't ready to move to Python 3 yet. It's looking very likely that we'll be making the leap for new development starting in the next week or so.

Python 2 is a beautiful, wonderful language. Python 3 is even better and there are very few reasons not to adopt it now.

Re: Python 2.7.4 Released

#37

Post by gtaylor »

spullara wrote: post #23
tshepang wrote: post #21

Earlier quoted context omitted.

Why would you use/support the fork? Why not just upgrade?

It is pretty clear that the current users of Python 2.x have voted that they don't want to move to Python 3. Some language changes and lots of library changes. Everything has to be ported to upgrade.

As a current user of Python 2.x, I can't wait to make the jump to 3, and have already done so for a few of my personal projects. It's probably best not to generalize too much.

Re: Python 2.7.4 Released

#38

Post by legutierr »

spullara wrote: post #23
tshepang wrote: post #21

Earlier quoted context omitted.

Why would you use/support the fork? Why not just upgrade?

It is pretty clear that the current users of Python 2.x have voted that they don't want to move to Python 3. Some language changes and lots of library changes. Everything has to be ported to upgrade.

I've been waiting for Django and PyPy, personally, and they're both comming along at a satisfactory pace, in my opinion.

Re: Python 2.7.4 Released

#39

Post by landypro »

tshepang wrote: post #27
cerales wrote: post #26

It seems weird that large features like dictionary comprehensions and syntax changes like set literals are making it int0 2.7.x, but I'm not complaining - most of my projects are stuck on 2.7 due to deployment environment or library limitations and I'd love to be able to use these features.

If you read that page more carefully, you will notice that the list is about 2.7 changes, not 2.7.4.

If you read his reply more carefully, you would have realised he's talking about the move to Python 3.x

There aren't any libraries I know of that work in 2.7 but not 2.7.x

Re: Python 2.7.4 Released

#40

Post by SoftwareMaven »

legutierr wrote: post #38
spullara wrote: post #23

Earlier quoted context omitted.

It is pretty clear that the current users of Python 2.x have voted that they don't want to move to Python 3. Some language changes and lots of library changes. Everything has to be ported to upgrade.

I've been waiting for Django and PyPy, personally, and they're both comming along at a satisfactory pace, in my opinion.

I started a new Django project at work using Python 3. Fun part is it gives me an excuse to help some of the various Django libs to move to 3 (if the authors are still around to take pull requests :/).
Post reply on HN