[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

How to handle .in files during development

From: Martin Laabs
Subject: How to handle .in files during development
Date: Wed, 21 Oct 2020 17:20:03 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0


some parts (e.g. the ubxtool) are provided as .in files in the git repository which are converted to e.g. .py files during the installation.

My problem with that process is if there are changes required in the .in files. I could make all my changes in the (auto generated) .py file, test it, convert the .py file into a .in file manually and commit a big blob. Obviously, this is not a good programing practice.

The other way around would be: configure scons to convert the .in file prior each run to a .py file and run that file. However - this has the drawback that each change, accidentally made in the auto-generated file is lost and has some issues with code editor as well. (E.g. an exception is raised, the editor jumps to the line, you fix it and re-run the program just to see that it had no effect as the file was overwritten again ...)

Is there is a best practice how to deal with this situation?

Thank you,

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]