Add a new --pyvers argument to setup.py for specifying versions.

Review Request #11874 — Created Nov. 12, 2021 and updated

david
Review Board
release-4.0.x
reviewboard

Usually we'll want to set up development environments using
--all-pyvers, which will set up all supported versions. In some cases,
however, it can be useful to set up a subset of versions (for example,
right now Python 3.6 and 3.7 don't work correctly on Apple M1). This
change adds a new argument that allows doing something like
python setup.py develop --pyvers "2.7 3.8 3.9"

Used to set up a dev environment.

Summary
Add a new --pyvers argument to setup.py for specifying versions.
Description From Last Updated

Took me a second to realize what we were deleting here, since I was thinking "Oh, each Python version is ...

chipx86chipx86
Checks run (2 succeeded)
flake8 passed.
JSHint passed.
chipx86
  1. 
      
  2. setup.py (Diff revision 1)
     
     
     

    Took me a second to realize what we were deleting here, since I was thinking "Oh, each Python version is its own argument." Which of course isn't right, but since this whole block of code is really its own thing, can we document in here somewhere what the format of --pyvers is like, and what we're deleting here?

  3. 
      
david
  1. To be honest, this was prior to your pydo script, and I'm not really feeling like I care about this anymore. Opinions?

  2. 
      
Loading...