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

Fairseq 0.2.1 - No wheels available for PyTorch 2.3.* and 2.4.* #745

Open
julianzaidi opened this issue Aug 14, 2024 · 2 comments
Open

Fairseq 0.2.1 - No wheels available for PyTorch 2.3.* and 2.4.* #745

julianzaidi opened this issue Aug 14, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@julianzaidi
Copy link

julianzaidi commented Aug 14, 2024

Hey,

I try to install fairseq2 following the instructions in the README but it seems that no wheels are available for PyTorch 2.3.* and 2.4.*

Wheels for PyTorch 2.2.* seems to be there (e.g. https://fair.pkg.atmeta.com/fairseq2/whl/pt2.2.2/cu121). As a result, I have PyTorch 2.4.0 installed but it is automatically removed and replaced by PyTorch 2.2.2 when I try to pip install fairseq2.

As a side note, wheels for the nightly builds are available (e.g. https://fair.pkg.atmeta.com/fairseq2/whl/nightly/pt2.4.0/cu121), but I need fairseq2 0.2.1 not 0.3.0.dev*

Are you planning on adding those wheels for the 0.2.* versions?

Thank you!

@julianzaidi julianzaidi added the bug Something isn't working label Aug 14, 2024
@julianzaidi
Copy link
Author

@cbalioglu, sorry for the spam if you are not the right person. Do you plan on adding those wheels in a near future?

@lukasschmit
Copy link

Hi, wanted to bump this! The readme indicates that fairseq2 binaries are available for torch 2.5.1. The exact command in the readme:

pip install fairseq2 --extra-index-url https://fair.pkg.atmeta.com/fairseq2/whl/pt2.5.1/cu124

will just install the pypi fairseq2 as the provided url does 404's (as per OP's comment). The binaries DO exist for the nightly builds, but I also need for fairseq2 0.2.1.

Do this builds actually exist and the readme simply has the wrong URL, or are there no plans for fairseq2 to support newer torch versions and the "variants" / "nightly" sections of the readme have been intermixed erroneously?

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