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 pitrou
Recipients MizardX, antlong, eric.araujo, mdehoon, nadeem.vawda, niemeyer, pitrou, rhettinger, wrobell, xuanji
Date 2011-03-14.15:58:04
SpamBayes Score 2.6367832e-08
Marked as misclassified No
Message-id <1300118282.3720.4.camel@localhost.localdomain>
In-reply-to <1300116791.03.0.0380289082895.issue5863@psf.upfronthosting.co.za>
Content
> Regarding the use of PY_SSIZE_T_CLEAN, I assume that Py_ssize_t is to be
> preferred over plain ssize_t. Is this correct?

Yes, ssize_t doesn't exist everywhere AFAIK.
(size_t does, or at least we assume it does)

> Also, I was wondering whether I need to add some sort of license boilerplate to
> the beginning of bz2.py? With _bz2module.c, I presume I should retain the
> copyright information from the old bz2module.c. Would something like this be ok?

Well, I would personally advocate not re-adding a license boilerplate,
since it doesn't serve a purpose (nearly all of Python is freely usable
under the PSF License, and the authors are documented by version
control).
You could ask on python-dev to get other opinions, though.
History
Date User Action Args
2011-03-14 15:58:05pitrousetrecipients: + pitrou, rhettinger, niemeyer, mdehoon, wrobell, nadeem.vawda, eric.araujo, MizardX, antlong, xuanji
2011-03-14 15:58:04pitroulinkissue5863 messages
2011-03-14 15:58:04pitroucreate