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 baikie
Recipients baikie, vstinner
Date 2010-10-02.21:25:44
SpamBayes Score 7.758237e-09
Marked as misclassified No
Message-id <20101002212537.GA29167@dbwatson.ukfsn.org>
In-reply-to <1285781559.72.0.62593560462.issue9647@psf.upfronthosting.co.za>
Content
> If I understood correctly, you don't want the value to be truncated if the variable grows between the two calls to confstr(). Which behaviour would you expect? A Python exception?

A return size larger than the buffer is *supposed* to indicate
that the current value is larger than the supplied buffer, so I
would just expect it to reallocate the buffer, call confstr()
again and return the new value, unless it was known that such a
situation indicated an actual problem.

In other words, I would not expect it to do anything special.  I
didn't write the original patch the way I did in order to fix
this (potential) bug - it just seemed like the most natural way
to write the code.
History
Date User Action Args
2010-10-02 21:25:46baikiesetrecipients: + baikie, vstinner
2010-10-02 21:25:45baikielinkissue9647 messages
2010-10-02 21:25:44baikiecreate