-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
element_interface
not in requirements
#66
Comments
Thanks for the report @sneakers-the-rat. We opted not to keep element-interface in the |
you can require something from git in a requirements.txt file!
see https://pip.pypa.io/en/stable/topics/vcs-support/ I have several packages on PyPI that have git dependencies, so it's definitely allowed! for example: https://github.com/wehr-lab/autopilot/blob/637064da3d10e9eeb186483827c8b7dadaa2f356/pyproject.toml#L55 edit: coming back embarassed to say that while i have been publishing packages on pypi that have git dependencies for awhile, it apparently was only because of them being implicitly in a requirements.txt file (and thus not in the wheel's metadata), and when packaged correctly you are right that you can't put them up there! 🤦 |
element_interface
is imported from:element-array-ephys/element_array_ephys/ephys_chronic.py
Line 7 in 14517a2
but it's not in the requirements:
https://github.com/datajoint/element-array-ephys/blob/main/requirements.txt
so the module can't be imported.
The text was updated successfully, but these errors were encountered: