One issue here is that the last release of npyscreen was made over 5 years ago.

If it's a dependency of something else then the upstream of the consumers should be poked to migrate to urwid or Python Prompt Toolkit which are both active projects.

Yes, the last release was made over 5 years ago, however, there are still lots of projects that depend on it.

So it's better to have it rather than abandon them of support until they will migrate.

So it's better to have it rather than abandon them of support until they will migrate.

nixpkgs is not really mean to have every python package. Commonly used packages, callable script and dependencies of other software are usually not a problem.

Sure it's not, but right now I'm working on pushing some software to nixpkgs, and npyscreen is required for.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.

Result of nixpkgs-review pr 111157 run on x86_64-darwin 1

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.

Result of nixpkgs-review pr 111157 run on x86_64-linux 1