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

Graphene v3 following v3 graphql-core #1048

Merged
merged 9 commits into from
Aug 17, 2019
Merged

Graphene v3 following v3 graphql-core #1048

merged 9 commits into from
Aug 17, 2019

Conversation

mvanlonden
Copy link
Member

@mvanlonden mvanlonden commented Aug 9, 2019

Graphene compatibility with graphql-core v3

Order of operations:

  1. Approve and merge 988 into next/master Change dependency to graphql-core-next #988
  2. Create a v2 branch from master
  3. PR and merge next/master into master Graphene v3 following v3 graphql-core #1048
  4. Cut a v3.0.0a0 release from master

ekampf and others added 6 commits June 1, 2019 18:41
* Change travis to only compile for p3.6+

* Changed tox to only run Python 3.6+

* Changed library classifiers to reflect support in Python 3.6+

* Changed version to 3.0.0 development

In [15]: get_version((3, 0, 0, "alpha", 0))
Out[15]: '3.0.dev20190601212304'
We no longer need a dedicated folder for Python3.6+ tests
We no longer need to check six.PY3 in tests
* No one is using func_name

* Remove six simple usages

* Remove six requirement

* Remove `six.with_metaclass` calls
# Conflicts:
#	graphene/__init__.py
jkimbo and others added 2 commits August 9, 2019 19:12
* Changed dependencies to core-next

* Converted Scalars

* ResolveInfo name change

* Ignore .venv

* Make Schema compatible with GraphQL-core-next

* Ignore more venv names and mypy and pytest caches

* Remove print statements for debugging in schema test

* core-next now provides out_type and out_name

* Adapt date and time scalar types to core-next

* Ignore the non-standard result.invalid flag

* Results are named tuples in core-next (immutable)

* Enum values are returned as dict in core-next

* Fix mutation tests with promises

* Make all 345 tests pass with graphql-core-next

* Remove the compat module which was only needed for older Py version

* Remove object as base class (not needed in Py 3)

* We can assume that dicts are ordered in Py 3.6+

* Make use of the fact that dicts are iterable

* Use consistent style of importing from pytest

* Restore compatibility with graphql-relay-py v3

Add adpaters for the PageInfo and Connection args.

* Avoid various deprecation warnings

* Use graphql-core 3 instead of graphql-core-next

* Update dependencies, reformat changes with black

* Update graphene/relay/connection.py

Co-Authored-By: Jonathan Kim <[email protected]>

* Run black on setup.py

* Remove trailing whitespace
@mvanlonden
Copy link
Member Author

Blocked by #1054

Copy link
Member

@ProjectCheshire ProjectCheshire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks amazing - great work, everyone!

@mvanlonden mvanlonden merged commit 8e7d76b into master Aug 17, 2019
@@ -2,7 +2,7 @@ class _OldClass:
pass


class _NewClass(object):
class _NewClass:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This module can be simplified a bit now than Python 2 is not supported - this _OldClass and _NewClass stuff was purely to support Python 2.

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

Successfully merging this pull request may close these issues.

5 participants