Use enum34 backport when Enum is not available

[Nabellaleen]

Tests were broken in Python < 3.4, this PR fix its

[coveralls]

Coverage remained the same at 91.877% when pulling f8b3962 on Nabellaleen:fix-enum-backport-requirement into 6a96d37 on graphql-python:master.

[coveralls]

Coverage remained the same at 91.877% when pulling f8b3962 on Nabellaleen:fix-enum-backport-requirement into 6a96d37 on graphql-python:master.

[coveralls]

Coverage remained the same at 91.877% when pulling f8b3962 on Nabellaleen:fix-enum-backport-requirement into 6a96d37 on graphql-python:master.

[coveralls]

Coverage remained the same at 91.877% when pulling a61580a on Nabellaleen:fix-enum-backport-requirement into 8a2f020 on graphql-python:master.

[Nabellaleen]

I also fixed :

• setup.py to really allow launching tests by using python setup.py test
• README.md to give a working example for pytest arguments

[Cito]

See my inline comment in the last commit. Otherwise looks fine.

[Nabellaleen]

I added a commit fixing build issues, but they are mainly related to a wrong requirements management in setup.py and broken dependancies in graphql-core

All these things should be fixed propelry soon by work from @jnak on tox migration and from a PR on graphene / graphql-core

[jnak]

@Nabellaleen I'm almost done with the migration to tox. I'll be sending a PR tomorrow because I'm off today.

[Nabellaleen]

@jnak have a look at the change I made in this PR to take it into account in yours (but it's probably already the case ;))

[jnak]

@Nabellaleen Sounds good. I'll take a look tomorrow morning

[Nabellaleen]

Suggested change

	"rx<3.0.0",
	"rx<3.0.0", # Rx 3.0 or above are only compatible with Python >= 3.6

[jnak]

@Nabellaleen In case you're curious, here are the changes I worked on yesterday. In order to avoid duplicating work, I think it makes sense to hold on this PR for now and wait for my changes to be merged in. I'll be sending a PR tomorrow. Cheers

jnak@a4d5700

[Nabellaleen]

@jnak Yeah, I see ;) Great job ! I can't wait to see things move :D But I'll make an effort and be patient ;)

[jnak]

@Nabellaleen Thanks for re-enabling python 2.7.

Out of curiosity, what's the policy to merge PRs in this project? It looks like you were able to merge this PR without getting it approved by someone else.

[Nabellaleen]

@jnak Indeed, rules seems not enforced in the repository settings - I'll fix it !

For the graphene organisation, the rules were defined some weeks ago during a meeting, and are specific for each repository (between 1 and 3 approvals for a merge).

For graphene-sqlalchemy repository, it's 1 approval, so I should have been blocked for merging this one.