Honestly, I did not realize that 3.7 has been released by the time I wrote
my e-mail. I think it will be prudent to get this command back in Python
3.7.1. My work-around was to simply copy the 20-something lines that
define install_misc from Python 3.6 to my setup.py file.
It was my impression that it is precisely due to situations like this,
distutils was considered more or less frozen for development and all new
features went to setuptools.
On Fri, Jul 6, 2018 at 5:57 PM Victor Stinner
Hello,
I am not sure of what you propose. Do you want to get the feature back in
Python 3.7.1? If yes, should it start to emit a deprection warning?
Did you manage to workaround the removal? If yes, maybe we can add more
doc to the Porting section of What's New in Python 3.7?
Victor
Le jeudi 5 juillet 2018, Alexander Belopolsky <
I started porting my project [1] to Python 3.7 and came across bpo-29218:
"The unused distutils install_misc command has been removed." [2]
Historically, the distutils package was very conservative about changes because many 3rd party packages extended it in ways unforeseen by the Python core developers. As far as I can tell, this removal was done without a deprecation period or any public discussion.
The comment above the command class [3] was there for 18 years and
alexander.belopolsky@gmail.com> a écrit : promised to "keep it around for the time being." Why did it suddenly become necessary to remove it in 3.7? Is shedding 20 lines of code really worth the risk of breaking user code?
[1]: https://github.com/KxSystems/pyq [2]:
https://docs.python.org/3/whatsnew/3.7.html#api-and-feature-removals
[3]: https://github.com/python/cpython/commit/aae45f93e7b7708deb1ce9d69b58fa02910...