-
Notifications
You must be signed in to change notification settings - Fork 12
pyproject.toml
not in the main directory
#304
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
Comments
interesting 👀 |
Hi @szalpal Thanks for filing this issue! The underlying issue is also captured in #255, which is that xet-core repo is not laid out for building the Python package from the root of the repo. Instead, the Do you know how to specify a subdirectory for building when specifying a dependency for a Python package? |
As a workaround, I tried this:
But the cargo.toml is still at 1.0.3 and so hf-xet gets built using maturin to have that package version, which then has pip try to get & build the package again, which fails. I will work on moving the pyproject.toml to the root of the repo as a fix, and I will update our release process so the cargo.toml gets committed with the version being built.
|
This is fixed in the hf-xet 1.1.2 release. Please verify working on your end and close, thanks!
|
Hi,
When trying to build
tokenizers
for Python 3.13t, I think I noticed a problem insidexet-core
.tokenizers
depends onhuggingface_hub
, which with recent release introducedxet-core
dependency. When trying to buildtokenizers
from source (pip install git+https://github.com/huggingface/tokenizers.git#subdirectory=bindings/python
), build fails since 2nd-order dependency (xet-core
) can't be build. I believe it's because the build system expectspyproject.toml
to be inside main directory. I believe the problem occurs in Python 3.13t only, since it's a version that does not support Limited API (abi3
), therefore the build system can't downloadhf-xet
package and tries to build it from scratch.Issue that captures Python 3.13t support in
tokenizers
: huggingface/tokenizers#1767May I ask for confirmation, is this a real problem and shall it be tackled?
Steps to reproduce:
pyenv
)$ curl https://pyenv.run | bash $ pyenv install 3.13t $ pyenv global 3.13t
tokenizers
The text was updated successfully, but these errors were encountered: