> "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
Steve wrote:
> Just to clarify one thing: you don't need a special license to get Visual
Studio Community Edition to work on Python, even within a big company -
it's free for open source work, and has everything we need.
My employer gave me a laptop without Windows license. It is likely the case
f
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
