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

label-studio requirement incorrect, also getting old #7

Closed
RevelaAutumn opened this issue Mar 19, 2021 · 3 comments
Closed

label-studio requirement incorrect, also getting old #7

RevelaAutumn opened this issue Mar 19, 2021 · 3 comments

Comments

@RevelaAutumn
Copy link

The README example does not work as is -- label-studio==1.0.0 does not provide the command label-studio-ml, and does not expose LabelStudioMLBase.

It works OK with label-studio==0.7, but that's not what's specified in requirements.txt.

(NB that it also doesn't work with the current head of label-studios-ml-backend).

@RevelaAutumn RevelaAutumn changed the title Undocumented requirement for unknown version of label-studio-ml-backend label-studio requirement is getting old Mar 19, 2021
@RevelaAutumn RevelaAutumn changed the title label-studio requirement is getting old label-studio requirement incorrect, also getting old Mar 19, 2021
@niklub
Copy link
Contributor

niklub commented Mar 19, 2021

Hi, @RevelaAutumn ! Thanks reporting this. Can you please drop here an issue log of what's happening after connecting to label-studio-ml-backend ? (Indeed, the ML backend has been moved to a separate repo, but API hasn't changed)

@RevelaAutumn
Copy link
Author

RevelaAutumn commented Mar 19, 2021

Hi @niklub , I never even get there, the issue log would be

 ~ label-studio-ml
pyenv: label-studio-ml: command not found   

Really I'm just saying that the requirements.txt shouldn't permit label-studio v1.0 until the transformers project has been tested with it!

@niklub
Copy link
Contributor

niklub commented Mar 30, 2021

Hi, @RevelaAutumn
Label Studio 1.0. compatibility issues have been fixed in the latest master, please try it out and reopen the issue In case you get any problem

@niklub niklub closed this as completed Mar 30, 2021
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

No branches or pull requests

2 participants