On 01/06/2016 10:06 PM, Martin Panter wrote: > According to Larry > <https://mail.python.org/pipermail/python-dev/2015-December/142566.html>, > 3.4.4 was the last bug fix release for 3.4, so I assumed the 3.4 > branch should now be in security-fixes-only mode. You assume correctly. > However this branch > still seems to get a lot of non-security action, for example the most > recent bunch of changes were some work on the provisional “pathlib” > module. I haven't looked at the changes you mention (I'm on a trip) but... what am I to do? Beyond tagging all future 3.4 releases from a repository only I have write access to and never pulling from hg.python.org, I don't really have any power to enforce the condition. I'm left trusting the better judgment of the Python core dev community. I feel like a parent who's caught his kid reading after bedtime using a flashlight under the covers. I mean, no, that's not what you should be doing right now. But fixing bugs in Python is hardly the worst thing in the world. //arry/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160107/33ff8b4a/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4