Do note that is not as easy as it seems as you would have to figure out how to manage dependencies appropriately, especially if you are going to support using different versions at the same time.
Otherwise you could write your own function today to see if you can get a proof-of-concept working as the `import` statement isn't anything special and everything it does is implemented in Python already. On Wed, Jun 10, 2020 at 9:47 AM Aditya Shankar <[email protected]> wrote: > it'd be really cool if we could drop virtualenvs + requirements.txt > altogether, i.e., like deno, mordern javascript and so... > > i.e. instead of > `pip install package` > and > `import package` > and > `pip freeze > requirements.txt` > for every import, > > we stick to, for every python script > > `abc = import("package", "2.*")` > > from imports could be done like > > `value = import("package", "1.*").value ` > > this completely removes the virtualenvs issue, and solves alot of > problematic issues with python imports > _______________________________________________ > Python-ideas mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/FNQLJJMEDNPV3TWHVI6GFSEZWRUHY6M6/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/ZHAAJF7ITYPMDGZUVLBZNI63UZKKIASW/ Code of Conduct: http://python.org/psf/codeofconduct/
