Slashdot Mirror


Python 3.0 Released

licorna writes "The 3.0 version of Python (also known as Python3k and Python3000) just got released few hours ago. It's the first ever intentionally backwards-incompatible Python release."

15 of 357 comments (clear)

  1. good by Anonymous Coward · · Score: 4, Funny

    previous releases were incompatibilie with earlier ones unintentinally.

  2. Re:woohoo by Anonymous Coward · · Score: 5, Funny

    But I just came in here for an argument!

  3. from __future__ import braces by slumberheart · · Score: 5, Funny

    SyntaxError: maybe in 3.5

  4. Re:That marks my end of use for Python by lahvak · · Score: 4, Funny

    So what are you going to do, take all your existing Python applications and rewrite them in a different language, in order to avoid the "significant amount of work to maintain existing functionality with new language version"?

    --
    AccountKiller
  5. Re:And now to wait by morgan_greywolf · · Score: 5, Funny

    Nope. Python 3.11 for Workgroups.

  6. Re:Hey! by drewness · · Score: 4, Funny

    As someone mentioned above, try


    from __future__ import braces

    and see what happens. ;)

    As for Ruby, I don't really follow its development or use it, but I was reading just the other day that they're really focused on finishing 1.9, which does byte-compiling and some optimization. The current version (like JS before spidermonkey, V8, and squirrelfish) walks and executes the AST (as I understand it), which is slooow.

  7. I don't know why this story's flagged "endofdays" by Slartibartfast · · Score: 4, Funny

    That'll be when Perl 6.0 ships.

  8. Re:woohoo by Hal_Porter · · Score: 5, Funny

    No you didn't.

    --
    echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  9. Re:That marks my end of use for Python by moranar · · Score: 4, Funny

    Besides teh above remark of well thoguth migration paths - it is importante to remakr that support for python 2.x has not ended in any way.

    As far as Iam aware, the recomendation is to keep working with python 2.6 - and use the py2to3 script to regularly to make 3.0 releases if you you can ...

    Are you typing while drunk?

    --
    "I think it would be a good idea!"
    Gandhi, about Internet Security
  10. Re:woohoo by Chapter80 · · Score: 4, Funny
    GREAT!

    Interestingly, it IS backwards compatible in areas that you wouldn't think it should be. For instance, the following program takes the version number, adds one to it, and divides by two. You'd think it'd give a different answer between version 3 and version 2. Glad they kept this program working for me, as it's the secret production code that runs my multi-million dollar business.

    import sys
    version=int(sys.version[0])
    print (version+1)/2

    Prints 1 in either version. (on the bright side, 1/2 is now 0.5!)

  11. Re:I don't know why this story's flagged "endofday by Abreu · · Score: 4, Funny

    Signs of the apocalypse:

    * A black man was elected President of the US - November 4, 2008
    * Chinese Democracy was released - November 23, 2008
    * Python 3000 is released - December 4, 2008
    * ?
    * ?
    * Large Hadron Collider starts operations - ?
    * Duke Nukem Forever is released - ?

    --
    No sig for the moment.
  12. Re:woohoo by Random+BedHead+Ed · · Score: 5, Funny

    I think you should use a few more posts to explain the joke. The more you go on the funnier it gets. :)

  13. Re:And now to wait by Random+BedHead+Ed · · Score: 4, Funny

    This post was reserved for the Python NT 3.5 joke, but it has been postponed until the next release (along with a database-driven filesystem the Python developers swear they're working on).

  14. Re:woohoo by ValuJet · · Score: 5, Funny

    Yes it is.

  15. Re:woohoo by Chapter80 · · Score: 4, Funny
    OK. well, what I was aiming for was:

    True Part:
    In Python version 2, 1/2 = 1 (integer math)
    In Python version 3, 1/2 =0.5 (floating point math)

    Funny part:
    You can do some math on the version number and it comes out the same, even though the version number has changed. Because the divide operation changed too.

    wait, it's not so funny after all. What was I smoking?