python - Why does my installed app handle pkg_resources.iter_entry_points differently than in source? -
i have python app looks plugins via pkg_resources.iter_entry_points.
when run directly source checkout, find in sys.path fits bill, including source checkouts happen have applicable .egg-info setuptools find.
yet when install package anywhere via python setup.py install, ceases detect enumerated in sys.path, instead finding things installed alongside in site-packages.
- why
pkg_resources.iter_entry_pointsbehaving differently vanilla source checkout v. installed application? - how can make traverse in
sys.path, in development?
how iterate on sys.path?
pkg_resources.workingset(none).iter_entry_pointswhy behave differently? because installed package forces @ least meta data memory. looking @ code, guess main module has requires attribute, that's educated guess. anyway, force "installed" behaviour while developing, should enough run
python setup.py develop
Comments
Post a Comment