I like pkgs/development/python-modules only for modules (libraries).

awscli and aws_shell are CLI programs that just happen to be written in python so I don't really think they belong in the python-modules directory.

What do you think of this solution?

I like the idea of enforcing it, because not everyone reads the docs or the header of python-packages.nix. I have been thinking of having a bot for making such kinds of checks.

The part that maybe creates more confusion is the ${name} and the omission of a path. Is the name the pname? What if that suddenly does not work because the pname starts with capital letter and the folder does not. And where does it get the expression from?

I guess the other option is, why don't we put this inventory file under pkgs/development/python-modules/default.nix ? Then it would be fairly obvious that it's acting as an inventory.

This would indeed solve the latter issue.

awscli and aws_shell are CLI programs that just happen to be written in python so I don't really think they belong in the python-modules directory.

This is the real issue. I don't think the issue is that people want to import from other locations, I think the issue is that people are not aware of the reason and the difference that is made between applications and libraries.

Alright, I reverted the awscli and aws_shell changes so the only remaining thing is that path-enforcing function for python-modules.nix. I don't care a lot of this PR so I might just close it.

The part that maybe creates more confusion is the ${name} and the omission of a path. Is the name the pname? What if that suddenly does not work because the pname starts with capital letter and the folder does not. And where does it get the expression from?

The name is actually a relative path to the python-module. I expect most of the times it will match the pname but it's not necessary.