Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Updating to 36.5.0 breaks tests
See original GitHub issueTrying to update the package in Fedora from 36.2.0 to 36.5.0 produces some test failures with the message:
RuntimeError: maximum recursion depth exceeded while calling a Python object
Attaching two different build logs where tests are invoked under python2 and under python3 respectively.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:25 (25 by maintainers)
Top Results From Across the Web
Python break during install - CryoSPARC Discuss
I'm trying to install cryoSparc on a new box for us. However, I'm getting a new error during install that I don't know...
Read more >tdd - What to do when a new feature causes existing unit tests ...
Implement the feature first, run tests to see failures, and update or remove any failed tests (adding any more as necessary). Add new...
Read more >Best practices for writing unit tests - .NET - Microsoft Learn
Learn best practices for writing unit tests that drive code quality and resilience for .NET Core and .NET Standard projects.
Read more >Bicycle Friendly America Awards Lists and Profiles
You can also by updating your account at anytime. ... ABC s New Game Show · 4th of July Trivia Questions and Answers...
Read more >Army Combat Fitness Test - US Army
All permanent profiles must be updated by the Soldier's medical provider to reflect the ACFT events permitted or prohibited. Soldiers must test on...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @hroncok, thanks for the investigation!
Indeed your assessment seems correct. Created pytest-dev/pytest#2939 to track it, I will try to get to it soon.
Fedora package has been “fixed” by using
PYTHONDONTWRITEBYTECODE=1. I agree we can close this (I cannot close).