-
Notifications
You must be signed in to change notification settings - Fork 11
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
Migrate to tox 4 #332
base: master
Are you sure you want to change the base?
Migrate to tox 4 #332
Conversation
508f602
to
01de4fa
Compare
7ab704e
to
2b766be
Compare
If switching the extra name from |
fdadfe9
to
e40457a
Compare
Shall we defer this to post-release, so that things are roughly in sync with #333 ? |
As we discussed in-person the other week, I think this is for the best. |
This is looking pretty good except that, bafflingly, the |
Fixed! This is looking good. The main concern now is that it requires a different tox version from the release tests, so they can't use the same The simplest solution could be to hard-code the tox version in test_release.yml until it is migrated; we don't expect to bump it before it is migrated to tox 4 and using ci_requirements.txt again. |
tox.ini
to tox 4phonopy_reader
tophonopy-reader
for tox support (everywhere needed)pip install
command