Closed atztogo closed 1 year ago
Okey. So I think it would make sense at this point to follow upstream aiida-core
, then aiida-vasp
in parsevasp
. The test and lint environment etc. for aiida-core
is sensible and I do not see us having to do it differently. A huge upside is that it would then be much easier to work in editable mode and run pre-commit
on all three packages, which is certainly a use case, in particular for the latter two. Since aiida-vasp
depends on aiida-core
, otherwise it is not very useful, we can use for instance aiida-core[pre-commit]
in the pre-commit
extras as a dependency in aiida-vasp
. Unfortunately this installs the aiida-core
package as well, not just its dependencies. It would be ideal if we could use the same syntax and then tell the installer that we do not want the main package installed, only the listed dependencies. But that is not possible yet. For aiida-vasp
we can live with aiida-core
being installed in pre-commit
and for regular use and tests
it is surely needed anyway. But for parsevasp
we do not want this. We could rely on the depedencies also used by aiida-core
for pre-commit
but not aiida-core
itself. So right now, we try to follow those dependencies in a hard coded way. Not ideal.
And here, we see this showing up for Python 3.11 for pylint. The wrapt
fix should be in 2.13.0
, according to: https://github.com/pylint-dev/pylint/issues/5919#issuecomment-1067732808.
In fact, we need pylint~=2.15
as the wrapt
dependency was bumped from there on.
On my computer,
tox -e pre-commit
fails for python 3.11. This is probably fixed by using newer pylint. The issue is https://github.com/GrahamDumpleton/wrapt/issues/196. The version of pylint is fixed atsetup.json
, which causes the problem.But I see the version in
setup.json
is the same as that in aiida-core. So do we want to update it? The version of the pre-commit hook in.pre-commit-config.yaml
seems old. (Other hooks are also old.)