Hans Ekkehard Plesser
Hans Ekkehard Plesser
@jougs With the targets you propose, the typical approach for a developer who want to compile, install and test, ignoring anything to do with documentation, would then be ``` make...
`all` builds all the executable material, which is what I would expect of `all`. Documentation is something additional. So I think keeping `all` is fine.
@babsey Since #2022 is merged, could you take another look at this one?
Should we also put Pandas on that list. It is not absolutely necessary, but some tests will be skipped if it is not present and it is a very widely...
> Correction: matplotlib and scipy are optional. Pandas seems to be optional as well (imports wrapped in try..except). Yes, Pandas is optional in the sense that it will be skipped...
Strictly speaking, `cythonize` is build requirement, but not an install requirement, if you install from a wheel or similar that has all binary components pre-built?
@clinssen Any updates?
> For some reason, after bringing the branch up to date with master, the static code check does not pass anymore. > If I understand the output correctly, the errors...
I agree with @clinssen that additional version numbering schemes would induce more complexity with limited benefits. If we stick to semantic versioning logic for NEST (https://semver.org), backward-incompatible changes should only...
I would suggest to switch to flake8. There are just some cases where noqa is sensible.