Releases: IBM/import-tracker
Releases · IBM/import-tracker
1.3.0 - Import Stack Tracing
Change Log
- Add option to include stack trace information for imports (#27)
1.2.0 - Limited recursion sub-modules
1.1.1 - Handle degenerate dynamic modules
Change Log
- Fix handling of modules created using
imp.new_module
(#26)
1.1.0 - Side Effect Modules
Change Log
- Add support for specifying modules with side effects that should always be imported (#24)
1.0.2 - Allow compiled third-party libs
Change Log
- Fix tracking for third-party libraries that are compiled as
.so
files (eg viacython
) (#23)
1.0.1 - Fix Lazy Import Error Tracking
Change Log
- Fix tracking for libraries that use
lazy_import_errors
(#22)
1.0.0 - Initial Release
Change Log
This is the initial "official" release! It provides a set of stable uses:
- Run directly:
python3 -m import_tracker --name <my_module>
- Enable lazy import errors:
with import_tracker.lazy_import_errors(): ...
- Programmatically determine arguments to
setuptools.setup
:import_tracker.setup_tools.parse_requirements(...)
0.0.8 - All requirements group
Change Log
setup_tools.parse_requirements
now adds a special"all"
group toextras_require
that will alias to the union of all optional dependency sets
0.0.7 - Setup Tools and Lazier Errors
Change Log
- Add new
import_tracker.setup_tools.parse_requirements
that produces therequirements
andextras_require
arguments forsetuptools.setup
- Defer import errors further so that most import-time attribute usage does not raise for missing optional dependencies
- For imports with no known package mapping, assume the import name is the package
- Expose
LazyModule
as part of the public API since its useful for consuming projects
0.0.6 - Get tracked imports
Change Log
- Add
get_tracked_imports
to allow libraries to introspect all of their tracked imports