I tried to run “pysetup metadata” in a docutils source directory but the program failed, because packaging tries to import docutils and it picks up the 2.x version in the local directory.

The import chain is: pysetup → packaging.run → packaging.metadata → docutils

I could edit sys.path in pysetup, but that would mean that people calling “python3.y -m packaging.run” would not get the fix.  Another idea would be to catch both ImportError and SyntaxError when packaging.metadata tries to import docutils, but it would be better to find the 3.x version of docutils in site-packages if it exists.

What do you import experts think?

Due to the same reason, it’s also not possible to run “pysetup3.1 metadata” in the distutils2 repo, or “pysetup2.4 metadata” in the distutils2-python3 repo.

This is a problem on my side, not in distutils2.  My pysetupX.Y scripts are just shell one-liners of this form:

  PYTHONPATH=~/path/to/d2 pythonX.Y -m distutils2.run "$@"

Because of sys.path initialization, d2 tried to import docutils from the working directory instead of the version in site-packages.  If I install d2 and run the installed pysetup script, d2 and docutils are imported from site-packages and everything is fine.