Ensure compat with xdist 2.0+

[Zac-HD]

Fixes #17; see pytest-dev/pytest-xdist#541 for background.

---

This change is 

[coveralls]

Coverage remained the same at 58.197% when pulling 9276307 on emancipate into e06fec1 on master.

[bubenkoff]

please bump the version requirement for xdist accordingly
also, this should be a major release
and when you add a changelog record, don't assume the release already, this IMO should be done as part of the release process, so we keep unreleased changes under Unreleased instead of the number

[Zac-HD]

This is compatible back to pytest-xdist 1.22.3, which is older than the current minimum requirement 🙂

It's therefore an entirely internal change - this is an implementation detail which doesn't change any public API or dependencies, just ensures that users can upgrade pytest-xdist without breaking pytest-cloud.

[bubenkoff]

@Zac-HD then why the tests didn't fail before? then we should make sure that it's covered

[Zac-HD]

The new version of xdist hasn't been released yet - I'm aiming to update all the major integrations first.

And it's definitely covered, we're just switching to use the newer of two identical attributes before the old one is removed - so it's a no-op change on current versions but will not break when the next version comes out.

[Zac-HD]

@bubenkoff - I've fixed the changelog to list this as "Unreleased". If there's anything else I need to do before you can merge this, please let me know!

It's working at the moment but without this backwards-compatible patch pytest-cloud will break as soon as pytest-xdist 2 is released 😕

[bubenkoff]

please merge with squashing
would you like to get the pypi permission to release it yourself, now and in the future?

[Zac-HD]

Thanks @bubenkoff!

While I appreciate the offer, I'm happy to leave the release process to someone more regularly involved. Personally I like to automate releases entirely, so that CI tries a twine upload if the build passes on master, so I'm seriously out of practice at any manual release process 😅

[bubenkoff]

@Zac-HD if you're willing to help, let's automate it for this project?

[bubenkoff]

5.0.0 is out

[Zac-HD]

It's pretty easy! For hypothesis-jsonschema, here's the logic:

# to run in CI, on master, if tests pass:
python -m pip install --upgrade pip setuptools wheel twine
python setup.py sdist bdist_wheel && twine upload --skip-existing dist/*

And I wrote some tests to check that the version number and changelog are up to date too: https://github.com/Zac-HD/hypothesis-jsonschema/blob/master/tests/test_version.py

[bubenkoff]

@Zac-HD great, are you interested in helping set it up?