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
Which llama.cpp modules do you know to be affected?
Other (Please specify in the next section)
Problem description & steps to reproduce
do a pip install gguf inside of a conda env. Now the package has created both a /scripts/ and an /examples/ inside your site-packages.
I'm not sure it's particular to my environment, but running any other project with a /scripts/ folder has a relatively high chance of trying to import from GGUF "scripts" instead of it's own folder, at least on py 3.10.
If there is any other reason this happens, let me know. I have now checked 2 environments where I had to install GGUF and both have this issue. The solution is to simply delete the offending folders but you now have lost the scripts. Should they not be in the gguf folder so that it's gguf/scripts?
First Bad Commit
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Name and Version
https://pypi.org/project/gguf/ latest
Operating systems
Linux
Which llama.cpp modules do you know to be affected?
Other (Please specify in the next section)
Problem description & steps to reproduce
do a
pip install gguf
inside of a conda env. Now the package has created both a /scripts/ and an /examples/ inside your site-packages.I'm not sure it's particular to my environment, but running any other project with a /scripts/ folder has a relatively high chance of trying to import from GGUF "scripts" instead of it's own folder, at least on py 3.10.
If there is any other reason this happens, let me know. I have now checked 2 environments where I had to install GGUF and both have this issue. The solution is to simply delete the offending folders but you now have lost the scripts. Should they not be in the gguf folder so that it's gguf/scripts?
First Bad Commit
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: