Skip to content

Conversation

@pganssle
Copy link
Member

We'll need to pin pytest at version >= 2.0 if we want to use skipIf, and we'll need skipIf if we want to avoid calling pytest.warns on Python 3.2.

While I was in there I did a bit of cleanup.

@pganssle pganssle added the tests label Nov 12, 2017
@pganssle pganssle added this to the 2.7.0 milestone Nov 12, 2017
@pganssle pganssle force-pushed the fix_test_requirements branch from c65782e to 825c660 Compare November 12, 2017 17:22
@jbrockmendel
Copy link
Contributor

This generally looks good. Not sure if we should still be supporting 3.2, though that decision doesn't need to be made here.

@pganssle
Copy link
Member Author

Yeah, I think after the 2.7.0 release we can drop 3.2 support, but we really should be cutting a new release soon and there's no urgent need to remove 3.2 support.

@pganssle pganssle merged commit dd286a3 into dateutil:master Nov 12, 2017
@pganssle pganssle mentioned this pull request Mar 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants