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

Update Transformers and AllenNLP Requirements #56

Merged
merged 4 commits into from Aug 2, 2022

Conversation

Sophylax
Copy link
Member

With Transformers 4.18, we can use the new versions of transformers. There was a range of versions before that had a typing error which caused errors.

The earliest version of AllenNLP that supports 4.18 is 2.9.3. Which then had a bug with cached-path being updated and breaking some of the things on their side. 2.10.0, therefore, is the earliest version we can support with the new transformer requirement (and currently is the latest version).

@Sophylax
Copy link
Member Author

Turns out the black requirement in dev also needs to be updated. (There is a bug with click being updated, it was either that or fix click version.) I believe adding that to this PR is still in scope (which is updating requirements).

requirements.txt Outdated
@@ -1,8 +1,8 @@
allennlp>=2.3.0,<=2.9.0.dev20211215
allennlp==2.10.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't we relax this to >= ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just allennlp>=2.10.0 feels too open. Maybe with <2.11 as well?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea, also it is the common practice.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@@ -1,8 +1,8 @@
allennlp>=2.3.0,<=2.9.0.dev20211215
allennlp==2.10.0
datasets>=1.13.0,<2.0
deepdiff>=5.2.0
jury>=2.1.0,<3.0
numpy>=1.21.2
seqeval==1.2.2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not related to your changes but I wonder if we can support >= in seqeval and tensorboardX as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can check it if you want, but it might take some time. Maybe we can make it an issue and look at it separately?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it would be good as a remainder too even if we do not find time for that now.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#57 is created.

Copy link
Contributor

@cemilcengiz cemilcengiz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@cemilcengiz cemilcengiz merged commit 4c7ce1f into main Aug 2, 2022
@Sophylax Sophylax deleted the update-requirements branch August 11, 2022 13:18
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

Successfully merging this pull request may close these issues.

None yet

2 participants