This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author larry
Recipients larry, ncoghlan, serhiy.storchaka, zach.ware
Date 2014-01-26.14:02:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390744941.56.0.0539875742197.issue20396@psf.upfronthosting.co.za>
In-reply-to
Content
A minor bug, but still one that could cause confusion.  It's already bitten me once.

If I change the code generator in clinic.py, then --make everything, files using the "file" destination often won't change.  All the changes to the generated code will go in the generated file.  And since the UNIX build process ignores those generated files, it doesn't rebuild the source file.  I'd have to use "--make -f".

This won't just happen to me though.  If you update your trunk and run "make clinic" this could easily happen to you too.

I propose that Clinic handle this as follows: if the generated file changes, but the source file does not, it "touches" the source file.  (Technically I'll probably just rewrite the source file, as I already have code that does that.)
History
Date User Action Args
2014-01-26 14:02:21larrysetrecipients: + larry, ncoghlan, zach.ware, serhiy.storchaka
2014-01-26 14:02:21larrysetmessageid: <1390744941.56.0.0539875742197.issue20396@psf.upfronthosting.co.za>
2014-01-26 14:02:21larrylinkissue20396 messages
2014-01-26 14:02:21larrycreate