Skip to content
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

Remove unittest2, return to unittest #6062

Merged
merged 3 commits into from
May 26, 2024

Conversation

davidlowryduda
Copy link
Member

We are currently using a custom-modified unittest2, which itself was a modified version of the standard library package unittest.

Originally, unittest2 allowed people to use later versions of unittest in early 2.* versions of python. It also backported certain utilities from python's 3.4 version of unittest back to python2.

We don't use python2 anymore. We don't need unittest2 anymore. This commit removes all unittest2 and removes the custom unittest2 dependency.

We are currently using a custom-modified unittest2, which itself was a
modified version of the standard library package unittest.

Originally, unittest2 allowed people to use later versions of unittest
in early 2.* versions of python. It also backported certain utilities
from python's 3.4 version of unittest back to python2.

We don't use python2 anymore. We don't need unittest2 anymore. This
commit removes all unittest2 and removes the custom unittest2
dependency.
@davidlowryduda
Copy link
Member Author

As additional background, I'll note that I was experiencing a testing heisenbug that sometimes affected me (and the CI on my fork). I talked about this with David Roe and Edgar, but it felt really mysterious. This doesn't solve that heisenbug.

@roed314
Copy link
Contributor

roed314 commented May 21, 2024

Fine with me.

@edgarcosta
Copy link
Member

should we add unittest to requirements.txt?

also, given that you touched, I would consider removing install-deps.sh. @roed314 do you agree?

@roed314
Copy link
Contributor

roed314 commented May 21, 2024

Yes, I think removing install-deps.sh and adding unittest to requirements.txt is a good plan.

@davidlowryduda
Copy link
Member Author

We don't need to add unittest to requirements.txt because it's in the python standard library.

@AndrewVSutherland
Copy link
Member

This is likely going to fail the CMF tests as well, but if that is all that fails I will merge it.

@AndrewVSutherland AndrewVSutherland merged commit 4c35ab8 into LMFDB:main May 26, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants