Slashdot Mirror

← Back to Stories (view on slashdot.org)

Python Family Gets a Triplet Of Updates

Posted by timothy on from the responding-to-constrictive-criticism dept.

The Python developers have been busy this weekend, releasing three new versions at different points on the Python continuum: 2.7.4 (a 2.7 series bugfix release), 3.2.4 (what's new), and production releases 3.3.1. Here's what's new in 3.3.1.

4 of 196 comments (clear)

  1. Where is the 64 bit dongle support by PhamNguyen · · Score: 5, Funny

    Python needs to support larger dongles.

  2. 2.7.4 by JanneM · · Score: 5, Interesting

    Happy to see another bugfix release for 2.7. Like it or not, 2.7 is going to remain the main or only version of Python for years to come at many installations. Which means tools that depend on Python at such places also only or mostly support the 2.7 series.

    The developers for the tool I use have just only begun discussing the possibility of perhaps beginning support for Python 3 in addition to the 2.5-2.7 versions for unspecified later versions; but only if it is possible to do without too much code duplication and maintenance efort.

    --
    Trust the Computer. The Computer is your friend.
  3. Re:The Python Launcher by Anonymous Coward · · Score: 5, Informative

    PEP 397 doesn't do what you think it does. It's a program that gets installed when you install Python. It parses a .py file's shebang line and uses that to determine which installed version of Python gets called. It's not designed to bundle Python programs into standalone executables. For that, you'll want to download something like http://cx-freeze.sourceforge.net/ (which works on Python 3, unlike Py2EXE)

  4. Re:Add curly braces and you have C by mrvan · · Score: 5, Informative

    [...]And such stupendous stupidities such as isoweekday() returning a range of 1..7 [...]

    Maybe, from a CS point of view, any index should always be zero-based. However, for weekday there are two compelling arguments why this should not be the case:

    1) Authoritative: The ISO specs clearly state that weekday number should be 1..7 [from wikipedia: A date is specified by the ISO week-numbering year in the format YYYY, a week number in the format ww prefixed by the letter W, and the weekday number, a digit d from 1 through 7, beginning with Monday and ending with Sunday."]. So, any library that returns an "ISO week day number" of 0 is simply non-compliant

    2) Customary: All human readable date components are 1-based (the first "CE" date is 0001-01-01, not 0000-00-00). So why should weekday (which is intended for human consumption) be different?