Skip to content
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

Installability of PyHARP. #3

Open
cwitkowitz opened this issue Nov 1, 2023 · 0 comments
Open

Installability of PyHARP. #3

cwitkowitz opened this issue Nov 1, 2023 · 0 comments

Comments

@cwitkowitz
Copy link
Contributor

I am running into some weird behavior when attempting to install PyHARP. It seems that users should be able to install PyHARP to their python environments with pip install git+https://github.com/audacitorch/pyharp.git#egg=pyharp.

With this command, PyHARP is successfully cloned, built, and installed, but for some reason import pyharp gives:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'pyharp'

Interestingly, the import works if PyHARP is installed with the command pip install -e git+https://github.com/audacitorch/pyharp.git#egg=pyharp. However, this clones PyHARP underneath a new directory src created in the current working directory. This is undesirable behavior, to me at least.

Note that manually cloning and installing (as demonstrated in the README) also works, but there needs to be an installation method than can be condensed to one line of code in a requirements.txt file for HuggingFace.

In the past I have had no issues with pip install git+https://github.com/<username>/<reponame>, so I'm wondering why the -e flag is required and why it is creating a src directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant