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

s32cinemagoer.py issues #454

Open
bachlava4eva opened this issue Apr 28, 2023 · 9 comments
Open

s32cinemagoer.py issues #454

bachlava4eva opened this issue Apr 28, 2023 · 9 comments
Assignees
Labels
bug help needed s3 the new IMDb dataset

Comments

@bachlava4eva
Copy link

Issue description

This isn't working for me, and I'm not much of a programmer, so unfortunately I can't diagnose it properly

This line is creating an issue with the "encoding" somehow
engine = sqlalchemy.create_engine(db_uri,encoding='utf-8', echo=False)

I'm getting the following error, even if I remove the encoding, etc.:

TypeError: MetaData.create_all() missing 1 required positional argument: 'bind'

I'm not sure what is going on. Is anyone able to still use this? I'm on Python 3.11 on the latest version of the cinemagoer library

@bachlava4eva
Copy link
Author

bachlava4eva commented Apr 28, 2023

imdb\parser\s3_init_.py", line 65 also has the line: encoding='utf-8', which is causing errors for some reason

@bachlava4eva
Copy link
Author

I'm on sqlalchemy v.2.0.11

@bachlava4eva
Copy link
Author

Yeah so, the solution is to move back to sqlalchemy v1.4

@alberanid alberanid self-assigned this Apr 30, 2023
@alberanid alberanid added bug s3 the new IMDb dataset labels Apr 30, 2023
@alberanid
Copy link
Collaborator

I think we have some options:

  1. force the use of 1.3 >= SQLAlchemy <= 1.4 in the requirements,
  2. update the code to only use SQLAlchemy >= 2.0 (and force it in the requirements),
  3. update the code to be able to use any version above 1.3

Option 3 is probably the nicer to the users, but I don't known how much effort it would take.

Does anyone have some experience migrating from SQLAlchemy 1.4 to 2.0?

@bachlava4eva
Copy link
Author

I'm totally fine with using the different versions. Is there somewhere in the documentation that details which libraries and versions to use? I'm a beginning programmer, so I don't always know where to find this stuff haha

@alberanid
Copy link
Collaborator

the list of dependencies is in the requirements.txt file.

Before we can take a decision, we have to find out:

  1. how different would be the code from 1.4 to 2.0
  2. if it makes sense to support both
  3. how widespread are 1.4 and 2.0

@bachlava4eva
Copy link
Author

Thank you! I'm sorry I'm such a noob haha

@RealTehreal
Copy link

For all those Python-unaware people out there (like I am), here on how to exactly make it work:

pip install --upgrade sqlalchemy==1.4

Now, the error should be gone.

You're welcome.

@jimlynnjulian
Copy link

Unless I'm mistaken, some versions of SQAlchemy rely on an SQL library that has been removed from use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug help needed s3 the new IMDb dataset
Projects
None yet
Development

No branches or pull requests

4 participants