[Python-Dev] question re: default branch and release clone
Now that the 3.3 release clone has been created, can someone clarify what changes are allowed to go into the default branch? Is it the same policy as if the changes were going into the release clone directly (i.e. code freeze unless you have Georg's approval), or are future changes for 3.3.1 okay, or is the default branch for changes that would go into 3.4? If the policy is the same, when and how do we anticipate changing things for the default branch? Thanks, --Chris ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Sphinx issue in What's New in Python 3.3 doc
Hi, In the first example of the "PEP 409: Suppressing exception context" section, I read "from None...". http://docs.python.org/dev/whatsnew/3.3.html#pep-409-suppressing-exception-context It's confusing because I don't remember what was the last choice for the PEP: None or ... :-) The reST "code" looks correct in Doc/whatsnew/3.3.rst: ... raise AttributeError(attr) from None ... Victor ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] question re: default branch and release clone
On 26.08.2012 21:15, Chris Jerdonek wrote: Now that the 3.3 release clone has been created, can someone clarify what changes are allowed to go into the default branch? Is it the same policy as if the changes were going into the release clone directly (i.e. code freeze unless you have Georg's approval), or are future changes for 3.3.1 okay, or is the default branch for changes that would go into 3.4? If the policy is the same, when and how do we anticipate changing things for the default branch? Changes to the default branch must be bugfix-only. The 3.4 development only opens when the 3.3 branch is created, which happens after the release of 3.3.0 final. Changes made in default and not cherry-picked to the 3.3.0 release clone will therefore end up in 3.3.1 and 3.4. cheers, Georg ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Sphinx issue in What's New in Python 3.3 doc
On 26.08.2012 22:16, Victor Stinner wrote: Hi, In the first example of the "PEP 409: Suppressing exception context" section, I read "from None...". http://docs.python.org/dev/whatsnew/3.3.html#pep-409-suppressing-exception-context It's confusing because I don't remember what was the last choice for the PEP: None or ... :-) The reST "code" looks correct in Doc/whatsnew/3.3.rst: ... raise AttributeError(attr) from None ... Hi Victor, this is fixed in the latest Pygments, and will be fine in the doc once I update its version used for building. Until then, you could disable syntax highlighting on that particular code block. Georg ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
