> > The way I handled itnin importlib was to version check in setup.py and if > importlib would be in the stdlib I would use an empty list to represent > what to install
FWIW, that is also how I have done it in the past. Conditionally add install requirements to the list based on the current environment and then pass that to setup(). *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 Sat, Jul 11, 2015 at 12:50 PM, Brett Cannon <br...@python.org> wrote: > The way I handled itnin importlib was to version check in setup.py and if > importlib would be in the stdlib I would use an empty list to represent > what to install. That way users didn't have use markers and need to know > importlib was in some specific version of Python (basically argparse has > made people expect backports to just magically work). > > On Fri, Jul 10, 2015, 14:38 Ethan Furman <et...@stoneleaf.us> 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 > >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
