Always use virtualenv 20.x

[senpos]

• I have searched the issues of this repo and believe that this is not a duplicate.
• I have searched the documentation and believe that my question is not covered.

Feature Request

It is been a while, since virtualenv was completely rewritten.
The new version (20.x) and is a lot faster than both Python's built-in venv module and virtualenv 16.x.

It might be a good idea to always use new virtualenv 20.x in poetry.

At the moment, poetry uses virtualenv only for older Python versions.
In other cases, it uses venv.

I can see why Python may use an older and cut version of virtualenv in the standart library, it may be hard to maintain a bleeding-edge software.

But this change may add some value to such a modern dependency & enviroment management tool like poetry.

Would love to see poetry running even faster! :)

[finswimmer]

Hello @senpos ,

can you imagine more benefits beside that the initial creation of a venv reduces from 2 to 0.2 seconds?

fin swimmer

[pradyunsg]

@finswimmer You can find more details in the original RFC for the virtualenv 20.0 rewrite: pypa/virtualenv#1366

[senpos]

Since #2666 is merged, should I close the issue? :)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.