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

numpy version requirement while bittensor==8.0 #2334

Open
wjurkowlaniec opened this issue Oct 3, 2024 · 1 comment
Open

numpy version requirement while bittensor==8.0 #2334

wjurkowlaniec opened this issue Oct 3, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@wjurkowlaniec
Copy link

Describe the bug

When I want to have newest version of bittensor and tensorflow, I have clash of numpy requirement.

I can't have both installed in one project

To Reproduce

pip install tensorflow==2.17.0 bittensor==8.0

ERROR: Cannot install bittensor==8.0.0 and tensorflow==2.17.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    tensorflow 2.17.0 depends on numpy<2.0.0 and >=1.26.0; python_version >= "3.12"
    bittensor 8.0.0 depends on numpy~=2.0.1

Expected behavior

I should be able to install both.

I would suggest to lower version of numpy requirement, to at most 2.0.0

Screenshots

No response

Environment

OSX / Ubuntu

Additional context

No response

@wjurkowlaniec wjurkowlaniec added the bug Something isn't working label Oct 3, 2024
@wjurkowlaniec wjurkowlaniec changed the title numpy version requirement numpy version requirement while bittensor==8.0 Oct 3, 2024
@thewhaleking
Copy link
Contributor

Unfortunately, 2.0.0 would still not be compatible with tensorflow 2.17.0 (tensorflow 2.17.0 depends on numpy<2.0.0 and >=1.26.0;)

Tensorflow 2.18.0rc0: Requires-Dist: numpy <2.1.0,>=1.26.0
It is currently in rc0, which was released 30 September. Their typical release cadence is two weeks after rc0, so you've got roughly a week left until that happens.

I don't particularly want to go under numpy 2.0.1 for this, as it may require a bit of refactoring that would likely last roughly the same time as it takes for tensorflow 2.18.0 to fully release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants