#7984 make sure 'make fastlint' processes Python .in files
Closed: fixed 5 months ago by abbra. Opened 5 months ago by fcami.

As a developer I want 'make fastlint' to process our .in files like ipa-client-automount.in so that errors are found earlier.

You can't check .in files, because they are not valid Python files. I see two options:

1) Create the output files, then validate the output files (e.g. ipa-client-automount.in -> ipa-client-automount, then check ipa-client-automount)
2) Move all code out of the .in files into proper Python modules and convert the script files into two liners (import + main()).

I would prefer approach (2). The .in files have several disadvantages. The code is not reusable. IDEs don't recognize the files as Python files.

Thanks for the input @cheimes - after some experimentation #2 sounds like the best option.

Files to change:
and on a 2nd pass:
Those three can stay as-is:


  • 6d02edd Replace PYTHONSHEBANG with valid shebang


  • 452fe2f Replace PYTHONSHEBANG with valid shebang

For now I'll limit this to ipactl and ipa-client-automount.
We can do the others as we modify them.

Metadata Update from @fcami:
- Custom field on_review adjusted to https://github.com/freeipa/freeipa/pull/3296

5 months ago

Metadata Update from @fcami:
- Issue set to the milestone: FreeIPA 4.8

5 months ago


  • c0cf65c Move ipa-client-automount.in and ipactl into modules
  • b49c627 ipa_client_automount.py and ipactl.py: fix codestyle
  • 37ab150 Introduce minimal ipa-client-automount.in and ipactl.in


  • 6b2efdf Makefile.am: add .in files to fastlint target

Metadata Update from @abbra:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 months ago

Login to comment on this ticket.