Skip to content

Don't ship pam.py in the module #49

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AdamWill
Copy link

@AdamWill AdamWill commented Jul 4, 2025

The comment at the top of this file says:
"This is a legacy file, it is not used. Here for example." so it seems sensible to no longer ship it as part of the pam module itself. This moves it to an examples/ directory which will not be included in builds of the actual module, and updates the comment.

@AdamWill
Copy link
Author

AdamWill commented Jul 4, 2025

I'm not sure it makes any sense to include the file at all any more, but this is more conservative than just dropping it, I guess. Having it in the module itself just feels like a footgun. It means you can try to do import pam.pam, but it fails because it doesn't import __internals correctly.

The comment at the top of this file says:
"This is a legacy file, it is not used. Here for example."
so it seems sensible to no longer ship it as part of the pam
module itself. This moves it to an examples/ directory which
will not be included in builds of the actual module, and updates
the comment.

Signed-off-by: Adam Williamson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant