-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
max recursion depth in 3.1.2 #2485
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
Comments
This seems to be related to the specific version of py along with pytest 3.1.2 fails: 1.4.31 and 1.4.32 works: 1.4.33 and 1.4.34 |
Weird that it is failing for you, pytest requires py>=1.33 on |
Yes. I think this is not a bug. Just incompatible versions. I had a bad requirements.txt file. py==1.4.31 |
Even so, that should give some conflict... hmm although pip is known to not have true dependency resolution, that might be it. @bedwards should we close this? |
Yes, you can close it.
Regards,
Brian Edwards
(512) 584-6841
…On Fri, Jun 9, 2017 at 12:34 PM, Bruno Oliveira ***@***.***> wrote:
Even so, that should give some conflict... hmm although pip is known to
not have true dependency resolution, that might be it.
@bedwards <https://github.com/bedwards> should we close this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2485 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFat-rKcoFCpMPZ2FBR8Zbf2bVrf9czks5sCYIXgaJpZM4N1ipa>
.
|
There are conflicts between certain combinations of `pytest` and `py` that cause recursion issues (see pytest-dev/pytest#2501 and pytest-dev/pytest#2485). The same errors were showing up in Travis builds when pip pulled the most recent versions of these two packages.
I noticed my build started failing with a simple change to my source and tracked it down to grabbing the latest pytest. I have
pytest>=3
changing it topytest==3.1.1
works around the problem. I am using django-pytest 3.1.2.Attaching the traceback.
I will work on a minimal example. This is happening inside tox. It happens both on Mac OS X and on Bitbucket Pipelines (docker container running inside debian if I am not mistaken).
traceback.txt
The text was updated successfully, but these errors were encountered: