Basic python dependencies that are not included in EF2?

[AntonioSousa]

In EF1, there were a series of Python dependencies that we did not have to include. I even remember having to include "requests" in the very beginning, but then it was not needed anymore. At the time, that meant most extensions were reduced about >95% in size.

With EF2, we have to include a lot of dependencies that should be included by default, by using install_requires in setup.py. Why is this not the case anymore?

[Mike_L · Accepted solution]

In EF1 all extensions shared the same imports, so if one extension included a specific library, it was accessible by all. This caused conflicts whenever two extensions required to different versions of the same library. In EF2 each extension runs in its own virtual environment, so each extension has full control over what to import.