Skip to content
Discussion options

You must be logged in to vote

There's no way for spacy to use entry points like those for the additional architectures in spacy-transformers without loading the packages to some degree.

I would suggest filing an issue in the transformers repo because this could be updated to check for whether __doc__ is defined first, which they do in other places in the code. (I checked and couldn't find any related issues or PRs, but it's kind of hard to search for __doc__, so I might have missed something.)

(Also, due to issues with numpy and torch we haven't published spacy-transformers packages that support the very newest version of transformers yet, but I've tested newer releases of transformers and they were fine even if spacy…

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@xxyzz
Comment options

@xxyzz
Comment options

@adrianeboyd
Comment options

Answer selected by xxyzz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
third-party Third-party packages and services feat / transformer Feature: Transformer
2 participants