Seems to me this would be handled in the upstream packages that are
depending on enum34. IMO, it would be their responsibility to only
include enum34 if their package is being installed on a python that
needs it.
To ask enum34 to be installed and then expect enum34 to not install
itself seems backwards. But that's just my $0.02.
*Randy Syring*
Husband | Father | Redeemed Sinner
/"For what does it profit a man to gain the whole world
and forfeit his soul?" (Mark 8:36 ESV)/
On 07/10/2015 05:38 PM, Ethan Furman wrote:
I have recently received a request to make installing enum34 a no-op
on Python3.4 and later so that wheels, etc, don't have to worry about
the Python version when dealing with Enum.
From an enum34 point-of-view this makes sense since Enum is in the
stdlib in 3.4+, and enum34 has no purpose -- but how? Is it a simple
matter of checking for the Python version and raising SystemExit if
enum34 is not needed?
--
~Ethan~
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
