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

Error on all stl imports #1

Open
shashi792 opened this issue Nov 29, 2021 · 5 comments
Open

Error on all stl imports #1

shashi792 opened this issue Nov 29, 2021 · 5 comments

Comments

@shashi792
Copy link

import stl.parser as pr
import stl.parser as pr
import stl.utility as utl
import stl.cleaner as cln
import stl.column_classifier as cc

@LedZeppe1in
Copy link
Member

This error solved in dev branch. dev branch is current branch for development of TabbyLD2.

@shashi792
Copy link
Author

I copied the dev branch. It had the graphql_interface.py file missing. I copied this from the main branch. I get the following error.

  File "......PycharmProjects/tabby/tabbyld2/graphql_interface.py", line 5, in <module>
    from gql.transport.requests import RequestsHTTPTransport
  File "......anaconda3/envs/tabby/lib/python3.7/site-packages/gql/transport/requests.py", line 11, in <module>
    from requests_toolbelt.multipart.encoder import MultipartEncoder
ModuleNotFoundError: No module named 'requests_toolbelt
```'

Is there any updated graphql_interface.py file ?

@LedZeppe1in
Copy link
Member

graphql_interface.py file is not used. I have updated dev branch.
TabbyLD2 is currently under development (we are still far from the final version). I have almost implemented annotation of table cells.
Are you also engaged in semantic interpretation (annotation) of tables?

@shashi792
Copy link
Author

Are you also engaged in semantic interpretation (annotation) of tables?
Yes. But, it's a part of another use case.

I get the 404 error. I had some trouble installing the client.
image

Trying to work with the TabbyLD2 client (tabbyld2_client). Is this the only way to access the front-ends for the endpoint? (The use-case requires domain experts helping in annotations).

@LedZeppe1in
Copy link
Member

Yes. But, it's a part of another use case.
This is very good. I will be glad if you will use our developments.

Is this the only way to access the front-ends for the endpoint?
This is not the only way. Today, the run of TabbyLD2 is carried out only through main.py.
I updated dev branch and added information on installing and using TabbyLD2 in README.

PS: TabbyLD2 is far from complete. We partially implemented only annotation of table cells. We plan to implement annotation of columns and relationships between columns.

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