(original) (raw)
Thanks for the idea but there are currently no plans to support such a feature. If you would like to see it then you will need to write a PEP with a proof-of-concept to demonstrate how you would expect such a feature to work.
On Fri., May 17, 2019, 07:55 Q via Python-Dev, <python-dev@python.org> wrote:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_A lot of the Python code we use in production are used directly as imports in other pythondistributions (such as the python comes with the finite element software Abaqus and MSC Marc), manypackages (such as matplotlib, numpy) that may have varying versioned dependencies.I was wondering if this could be expanded to allow a version to be set within a package and havethat propagate to all modules in that package. For example in the root init.py if I setmultiversion(tornado, 2.2.1) then all modules in that package will use tornado 2.2.1 when I importtornado.See a relevant issue on github:Thank you!Qiang
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org