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 georg.brandl
Recipients Alexander.Belopolsky, SilentGhost, Trundle, belopolsky, georg.brandl, l0nwlf, ned.deily, sandro.tosi, vstinner, wsanchez
Date 2011-01-02.23:46:23
SpamBayes Score 6.890555e-07
Marked as misclassified No
Message-id <1294011997.61.0.317224980492.issue8013@psf.upfronthosting.co.za>
In-reply-to
Content
> There is a long tradition in keeping OS functions'
> wrappers thin with an expectation that application programmers will
> know the limitations/quirks of their target OSes.

Sorry, but that does not apply if we trigger undefined behavior which
is inherently unsafe, as you rightly insist.

I don't see the range checking as particularly challenging; I'm sure you can get it done in time for 3.2.
History
Date User Action Args
2011-01-02 23:46:37georg.brandlsetrecipients: + georg.brandl, belopolsky, wsanchez, vstinner, ned.deily, Trundle, SilentGhost, sandro.tosi, Alexander.Belopolsky, l0nwlf
2011-01-02 23:46:37georg.brandlsetmessageid: <1294011997.61.0.317224980492.issue8013@psf.upfronthosting.co.za>
2011-01-02 23:46:23georg.brandllinkissue8013 messages
2011-01-02 23:46:23georg.brandlcreate