[Python-Dev] RELEASED] Python 3.4.7rc1 and Python 3.5.4rc1 are now available
On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm relieved to announce the availability of Python 3.4.7rc1 and Python 3.5.4rc1. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. Python 3.4 now only receives security fixes, not bug fixes, and Python 3.4 releases are source code only--no more official binary installers will be produced. Python 3.5.4 will be the final 3.5 release in "bug fix" mode. After 3.5.4 is released, Python 3.5 will also move into "security fixes mode". Both these releases are "release candidates". They should not be considered the final releases, although the final releases should contain only minor differences. Python users are encouraged to test with these releases and report any problems they encounter. You can find Python 3.4.7rc1 here: https://www.python.org/downloads/release/python-347rc1/ And you can find Python 3.5.4rc1 here: https://www.python.org/downloads/release/python-354rc1/ Python 3.4.7 final and Python 3.5.4 final are both scheduled for release on August 6th, 2017. Happy Pythoning, //arry/ ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [python-committers] RELEASED] Python 3.4.7rc1 and Python 3.5.4rc1 are now available
2017-07-25 10:37 GMT+02:00 Larry Hastings : > On behalf of the Python development community and the Python 3.4 and Python > 3.5 release teams, I'm relieved to announce the availability of Python > 3.4.7rc1 and Python 3.5.4rc1. I checked for known security vulnerabilities: except of the issue #29606, all known vulnerabilties are fixed in these versions. It's ok, the issue #29606 is not fixed in master yet: https://bugs.python.org/issue29606 Victor ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Appending a link back to bugs.python.org in GitHub PRs
On Sat, Jul 22, 2017 at 12:28 AM, Brett Cannon wrote: > P.S.: Berker Peksag is working on providing commit emails with diffs in them > which is the other most requested feature since the transition. I forgot to give a status update on this. I deployed it on Heroku last week. You can see an example email at https://mail.python.org/pipermail/python-checkins/2017-July/151296.html --Berker ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] for...else
On 25/07/2017 06:51, Nick Coghlan wrote: On 25 July 2017 at 02:23, Ben Hoyt wrote: This is more of a python-ideas discussion, and Steven's answer is good. I'll just add one thing. Maybe it's obvious to others, but I've liked for...else since I found a kind of mnemonic to help me remember when the "else" part happens: I think of it not as "for ... else" but as "break ... else" -- saying it this way makes it clear to me that the break goes with the else. "If this condition inside the loop is true, break. ... *else* if we didn't break, do this other thing after the loop." For folks looking for a more in-depth explanation of the "if-break-else" approach to thinking about this construct: http://python-notes.curiousefficiency.org/en/latest/python_concepts/break_else.html A helpful explanation. But that it is necessary at all underlines that (IMHO) this use of 'else' is unnatural and hard to understand. I always have to think twice about it, whether reading it or using it myself. Therefore I would have preferred a more obvious keyword such as 'ifnobreak' (others may think of something better). But as has been stated, it's not going to change. Rob Cliffe That article also has a note explaining that we're unlikely to ever change this: http://python-notes.curiousefficiency.org/en/latest/python_concepts/break_else.html#but-couldn-t-python-be-different Cheers, Nick. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Appending a link back to bugs.python.org in GitHub PRs
With the linking back and forth, I'm curious why there wasn't a switch to use GitHub's issue tracker when we switched to GitHub. I'm sure there was previous discussion about this and good reasons not to, but couldn't find those quickly (PEP 512, Google search, etc) -- can someone point me in the right direction? -Ben On Fri, Jul 21, 2017 at 5:28 PM, Brett Cannon wrote: > Thanks to Kushal Das we now have one of the most requested features since > the transition: a link in PRs back to bugs.python.org (in a more > discoverable way since we have had them since Bedevere launched :) . When a > pull request comes in with an issue number in the title (or one gets > added), a link to bugs.python.org will be appended to the PR's body (the > message you fill out when creating a PR). There's no logic to remove the > link if the issue number is removed from the title, changed, or for > multiple issue numbers since basically those cases are all rare and it was > easier to launch without that kind of support. > > P.S.: Berker Peksag is working on providing commit emails with diffs in > them which is the other most requested feature since the transition. > > ___ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ > benhoyt%40gmail.com > > ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Appending a link back to bugs.python.org in GitHub PRs
On Tue, 25 Jul 2017 at 07:30 Ben Hoyt wrote: > With the linking back and forth, I'm curious why there wasn't a switch to > use GitHub's issue tracker when we switched to GitHub. I'm sure there was > previous discussion about this and good reasons not to, but couldn't find > those quickly (PEP 512, Google search, etc) -- can someone point me in the > right direction? -Ben > Basically there was push-back on the idea and I only had enough time and patience for one major infrastructure change that was somewhat controversial and not for two. -Brett > > On Fri, Jul 21, 2017 at 5:28 PM, Brett Cannon wrote: > >> Thanks to Kushal Das we now have one of the most requested features since >> the transition: a link in PRs back to bugs.python.org (in a more >> discoverable way since we have had them since Bedevere launched :) . When a >> pull request comes in with an issue number in the title (or one gets >> added), a link to bugs.python.org will be appended to the PR's body (the >> message you fill out when creating a PR). There's no logic to remove the >> link if the issue number is removed from the title, changed, or for >> multiple issue numbers since basically those cases are all rare and it was >> easier to launch without that kind of support. >> >> P.S.: Berker Peksag is working on providing commit emails with diffs in >> them which is the other most requested feature since the transition. >> >> ___ >> Python-Dev mailing list >> Python-Dev@python.org >> https://mail.python.org/mailman/listinfo/python-dev >> > Unsubscribe: >> https://mail.python.org/mailman/options/python-dev/benhoyt%40gmail.com >> >> > ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Am I allowed to use C++-style // comments?
https://www.python.org/dev/peps/pep-0007/ says two things: > Python versions greater than or equal to 3.6 use C89 with several select C99 > features: > [...] > C++-style line comments and also: > Never use C++ style // one-line comments. Which is it? -- Devin ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Am I allowed to use C++-style // comments?
On Tue, Jul 25, 2017, at 21:59, Devin Jeanpierre wrote: > https://www.python.org/dev/peps/pep-0007/ says two things: > > > Python versions greater than or equal to 3.6 use C89 with several select > > C99 features: > > [...] > > C++-style line comments This section overrides further edicts in the document for Python 3.6+. > > and also: > > > Never use C++ style // one-line comments. > > Which is it? ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Am I allowed to use C++-style // comments?
I actually realized right after I sent this that I am writing C++, so maybe it's a moot point. (Still trying to figure out how to use C for this, but it's an optional extension module only exposed for testing, so maybe it really doesn't matter.) Context is https://github.com/python/cpython/pull/2878 -- Devin On Tue, Jul 25, 2017 at 9:59 PM, Devin Jeanpierre wrote: > https://www.python.org/dev/peps/pep-0007/ says two things: > >> Python versions greater than or equal to 3.6 use C89 with several select C99 >> features: >> [...] >> C++-style line comments > > and also: > >> Never use C++ style // one-line comments. > > Which is it? > > -- Devin ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
