Expected behaviour

With recent changes to the Python packaging specification to allow the use of different backends, installing packages using setup.py often results in warning messages.

Actual behaviour

Regardless of your Python version, you will need to update your packaging specification to follow the latest Python packaging specification, PEP 517/518.

What are the steps to reproduce this issue?

There is no separate error implementation procedure for packaging specification changes, as they are not considered errors and can be categorized as feature enhancements.

Any other comments?

I'm working on changing the SQLAlchemy 1 version code to SQLAlchemy 2 version code in several subprojects of the Python-social-auth project, and I'd like to reflect this in the corresponding commits.

I guess it should be cherrypy.request.body_params or cherrypy.request.params or something like that

Expected behaviour

Version 2.0 of SQLAlchemy for social integration is being officially released on January 26, 2023, so if you install sqlalchemy with pip, version 2 will be installed automatically. However, the source code currently only works with SQLAlchemy 1.

As a result, all source code that uses SQLAlchemy will need to be modified to be compatible with SQLAlchemy 2.

Actual behaviour

This library should work fine with SQLAlchemy 2.

Any other comments?

I have made all the relevant updates and am currently working on testing them. I'll send a PR when I'm done testing. The branch I'm contributing to is feature/sqlalchemy2.

Expected behaviour

While testing the example-cherry project in the python-social-auth/social-examples project, I'm getting up to social login, but when I click the disconnect button, I get a 500 error.

Actual behaviour

The disconnect button should work properly after social login.

What are the steps to reproduce this issue?

You can clone the python-social-auth/social-examples project and set up a random provider in the example-cherry project and proceed with the social connection.

Any logs, error output, etc?

When you click the logout button, the console prints a message that the disconnect method received an unexpected csrfmiddlewaretoken argument, and the web browser throws a 500 error.

Any other comments?

I'm working on changing the SQLAlchemy 1 version code to SQLAlchemy 2 version code in several subprojects of the Python-social-auth project, and I'd like to reflect this in the corresponding commits.