-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
RFC: developer meta-environments #12789
Comments
MNE and mne-qt-browser both use qtpy so MNE-LSL could just transition I think.
Yes this one is bad -- MNE-Connectivity should be updated not to pin pytest.
MNE-NIRS doesn't use rtd theme nowadays actually I think the |
... FWIW generally speaking my process is to use a single dev env for as much stuff as possible, and if there are outliers that don't get along with the general Scientific Python practices, I give those a special isolated env. |
I also tend to use a single environment per project, and when I need an extra package installed in editable mode, I add it to the workspace and install it in the environment I want. I also tend to nuke my environments quite often because it's simpler and faster (especially with |
FYI,
Creating environments has never been so fast ;) |
This week I needed to recreate my dev env. As you may know, I develop/contribute to several related packages, so I often want/need editable installs of many things and to have all the optional dependencies installed (so I can run their tests, build their docs, etc). This makes things... hard. For example:
sphinx_rtd_theme
requiresdocutils<0.21
and its other (nested) dependencyreadme-renderer
requiresdocutils>=0.21.2
pytest<8
andpydata_sphinx_theme==0.14.1
(specially bad problem for me as I also develop that theme, but others may also want to do local MNE doc builds against current main of that theme)Possible solutions (please suggest others!)
thoughts?
The text was updated successfully, but these errors were encountered: