You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using import_tracker to manage a set of dependencies as optional in a large library, the problem of clean dependency management is deferred to the upstream library dependencies. Sometimes, those libraries also manage complex extras_require sets for various subsets of functionality. Currently, there is no way to subdivide the dependency on an upstream library across its extras_requires sets. For example:
requirements.txt
big_upstream[set1,set2]>=1.2.3
In this example, some modules in the library using import_tracker may require big_upstream, but may only use the parts of big_upstream from either set1 or set2. Currently, import_tracker will put big_upstream[set1,set2]>=1.2.3 into the extras_require set for all modules that require any functionality from big_upstream.
Describe the solution you'd like
The goal of this feature would be able to leverage the full set of dependency information for big_upstream[set1] and big_upstream[set2] independently such that individual modules within the import track'ed library can depend on these two extras sets independently.
Describe alternatives you've considered
Leave it as is and try to subdivide the upstream libs! Not terribly practical...
Additional context
The implementation of this would need to do the following:
Deduce the full set of modules required by each module+extras set listed in the requirements.txt (not sure if this is possible)
Use the full dependencies found when tracking a given module to cross-reference which module+extras set is needed for a given module, rather than using only the modules that appear in requirements.txt
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When using
import_tracker
to manage a set of dependencies as optional in a large library, the problem of clean dependency management is deferred to the upstream library dependencies. Sometimes, those libraries also manage complexextras_require
sets for various subsets of functionality. Currently, there is no way to subdivide the dependency on an upstream library across itsextras_requires
sets. For example:requirements.txt
In this example, some modules in the library using
import_tracker
may requirebig_upstream
, but may only use the parts ofbig_upstream
from eitherset1
orset2
. Currently,import_tracker
will putbig_upstream[set1,set2]>=1.2.3
into theextras_require
set for all modules that require any functionality frombig_upstream
.Describe the solution you'd like
The goal of this feature would be able to leverage the full set of dependency information for
big_upstream[set1]
andbig_upstream[set2]
independently such that individual modules within the import track'ed library can depend on these twoextras
sets independently.Describe alternatives you've considered
Leave it as is and try to subdivide the upstream libs! Not terribly practical...
Additional context
The implementation of this would need to do the following:
module+extras
set listed in therequirements.txt
(not sure if this is possible)module+extras
set is needed for a given module, rather than using only the modules that appear inrequirements.txt
The text was updated successfully, but these errors were encountered: