[Python-Dev] 2.6 branch in Mercurial?
I need to do a little 2.6 spelunking. I don't see a 2.6 branch in the output of "hg branches". Is "hg clone v2.6.9" the proper incantation to get the latest version (or perhaps "v2.6")? Thx, Skip ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2.6 branch in Mercurial?
On Oct 31, 2016, at 15:20, Skip Montanaro wrote: > I need to do a little 2.6 spelunking. I don't see a 2.6 branch in the output > of "hg branches". Is "hg clone v2.6.9" the proper incantation to get the > latest version (or perhaps "v2.6")? hg update -C v2.6.9 -- Ned Deily [email protected] -- [] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2.6 branch in Mercurial?
On Oct 31, 2016, at 15:25, Ned Deily wrote: > On Oct 31, 2016, at 15:20, Skip Montanaro wrote: >> I need to do a little 2.6 spelunking. I don't see a 2.6 branch in the output >> of "hg branches". Is "hg clone v2.6.9" the proper incantation to get the >> latest version (or perhaps "v2.6")? > > hg update -C v2.6.9 To expand a bit, that command will update to the 2.6.9 release. You don't see a 2.6 branch because it has been marked as closed. hg branches -c will show all branches. hg update -C 2.6 will update to the latest head of the 2.6 branch but that should essentially be the same as the tag v2.6.9. hg help branches -- Ned Deily [email protected] -- [] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2.6 branch in Mercurial?
On Mon, Oct 31, 2016 at 2:20 PM, Skip Montanaro wrote: > I need to do a little 2.6 spelunking. I don't see a 2.6 branch in the output > of "hg branches". Is "hg clone v2.6.9" the proper incantation to get the > latest version (or perhaps "v2.6")? 2.6 is a closed branch, which pretty much only means it doesn't show up in `hg branches`. Use `hg branches -c` to see it (beware that if you use the 'color' extension, the branch name may still be invisible due to coloring). -- Zach ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] [RELEASE] Python 3.6.0b3 is now available
On behalf of the Python development community and the Python 3.6 release team, I'm pleased to announce the availability of Python 3.6.0b3. 3.6.0b3 is the third of four planned beta releases of Python 3.6, the next major release of Python. Among the new major new features in Python 3.6 are: * PEP 468 - Preserving the order of **kwargs in a function * PEP 487 - Simpler customization of class creation * PEP 495 - Local Time Disambiguation * PEP 498 - Literal String Formatting * PEP 506 - Adding A Secrets Module To The Standard Library * PEP 509 - Add a private version to dict * PEP 515 - Underscores in Numeric Literals * PEP 519 - Adding a file system path protocol * PEP 520 - Preserving Class Attribute Definition Order * PEP 523 - Adding a frame evaluation API to CPython * PEP 524 - Make os.urandom() blocking on Linux (during system startup) * PEP 525 - Asynchronous Generators (provisional) * PEP 526 - Syntax for Variable Annotations (provisional) * PEP 528 - Change Windows console encoding to UTF-8 (provisional) * PEP 529 - Change Windows filesystem encoding to UTF-8 (provisional) * PEP 530 - Asynchronous Comprehensions Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.0b3 here: https://www.python.org/downloads/release/python-360b3/ Beta releases are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage maintainers of third-party Python projects to test with 3.6 during the beta phase and report issues found to bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2016-12-05). Our goal is have no changes after rc1. To achieve that, it will be extremely important to get as much exposure for 3.6 as possible during the beta phase. Please keep in mind that this is a preview release and its use is not recommended for production environments The next pre-release of Python 3.6 will be 3.6.0b4, currently scheduled for 2016-11-21. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily [email protected] -- [] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
