Neil Blakey-Milner <[EMAIL PROTECTED]> added the comment: This affects OS X too.
I'm attaching two patches - one uses malloc to build a bigger string if the existing implementation returns ERANGE, and the other one uses malloc from the start. This was done on the theory that stack memory use would be better/more efficient. However, based on testing, there's no real difference - 16.8usec vs. 17usec - on a rarely-used function. ---------- keywords: +patch nosy: +nbm versions: +Python 2.5 Added file: http://bugs.python.org/file10240/python-getcwd-dual-strategy.patch __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2722> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
