The (il-)logic of trying to apply copyright statements to an otherwise empty file should be weighed against the effort of writing a syntax checker that can ignore such files.
Generally, it's easier to script these things, so having a script that blindly adds the copyright header to all python files in the project (assuming there aren't files from other projects) is probably the best solution here. On Mon, Sep 9, 2013 at 2:21 PM, Doug Winter <doug.win...@isotoma.com> wrote: > > It is normal practice to include a brief license statement in every source > file, to make it clear what precisely is under the terms of that license. > > Cheers, > > Doug. > > > On 09/09/13 14:18, Jonathan Hartley wrote: > >> A small Python project of mine is apparently being included in Chromium, >> because I've had a bug report from them that my source files (plural) fail >> their build-time license checker. >> >> They'd like me to include a license and copyright info in every source >> file (including empty __init__.py files). >> >> I've responded that I don't want to be unhelpful, but I don't believe in >> putting duplicate license and copyright info in every source code file. To >> my mind, it belongs in a single central place, i.e. the project LICENSE >> file. >> >> Am I being unreasonable and/or daft? >> >> Jonathan >> >> > > -- > Telephone: +44 1904 567330, Mobile: +44 7879 423002 > Switchboard: +44 1904 567349, Fax: +44 20 79006980 > Post: Tower House, Fishergate, York, YO10 4UA, UK > > Registered in England. Company No 5171172. VAT GB843570325. > Registered Address: Tower House, Fishergate, York, YO10 4UA > > > ______________________________**_________________ > python-uk mailing list > python-uk@python.org > https://mail.python.org/**mailman/listinfo/python-uk<https://mail.python.org/mailman/listinfo/python-uk> >
_______________________________________________ python-uk mailing list python-uk@python.org https://mail.python.org/mailman/listinfo/python-uk