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
Following last night's discussion, I'm creating an issue to track Python code scanning in search of modules provided and dependencies required.
We want moss to auto-detect dependencies of Python packages, which isn't easy given the interpreted behavior of Python. We also want to track what modules a certain Python package provides, according to our tooling's goal.
Here I'm showing a proof-of-concept code that scans the site-packages directory and lists all modules a Python package contains. The code is short and simple, shouldn't be hard to port it to moss.
Dependencies are a different beast. In my script I'm commenting the difficulties, and what we can do about them.
Note that GitHub doesn't allow uploading .py files, so I'm renaming it into .txt. python_deps_provides.py.txt
The text was updated successfully, but these errors were encountered:
Following last night's discussion, I'm creating an issue to track Python code scanning in search of modules provided and dependencies required.
We want moss to auto-detect dependencies of Python packages, which isn't easy given the interpreted behavior of Python. We also want to track what modules a certain Python package provides, according to our tooling's goal.
Here I'm showing a proof-of-concept code that scans the
site-packages
directory and lists all modules a Python package contains. The code is short and simple, shouldn't be hard to port it to moss.Dependencies are a different beast. In my script I'm commenting the difficulties, and what we can do about them.
Note that GitHub doesn't allow uploading .py files, so I'm renaming it into .txt. python_deps_provides.py.txt
The text was updated successfully, but these errors were encountered: