If they're really all wontfix, maybe we should mark them as wontfix,
thus giving 3.4 a sendoff worthy of its heroic stature.
Godspeed, and may a flight of angels sing thee to thy rest,
//arry/
On 08/20/2018 05:52 AM, Victor Stinner wrote:
> "shutil copy* unsafe on POSIX - they preserve set
On 20/08/2018 14:52, Victor Stinner wrote:
>> "shutil copy* unsafe on POSIX - they preserve setuid/setgit bits"
>> https://bugs.python.org/issue17180
> There is no fix. A fix may break the backward compatibility. Is it really
> worth it for the last 3.4 release?
>
My idea would be to focus on a "fi
> "shutil copy* unsafe on POSIX - they preserve setuid/setgit bits"
> https://bugs.python.org/issue17180
There is no fix. A fix may break the backward compatibility. Is it really
worth it for the last 3.4 release?
> "XML vulnerabilities in Python"
> https://bugs.python.org/issue17239
Bug inactiv
“So that 3.4 dies in good health?”
More like getting all its evil deeds off its chest on the death bed, I think :)
Top-posted from my Windows 10 phone
From: Antoine Pitrou
Sent: Monday, 13 August 2018 2:59
To: Larry Hastings; python-committers; Python-Dev
Subject: Re: [python-committers] Winding
Le 13/08/2018 à 11:49, Larry Hastings a écrit :
>
>
> We of the core dev community commit to supporting Python releases for
> five years. Releases get eighteen months of active bug fixes, followed
> by three and a half years of security fixes. Python 3.4 turns 5 next
> March--at which point we
