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 neologix
Recipients ned.deily, neologix, r.david.murray
Date 2013-09-08.08:37:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM0rv+YZTQdjWz4dC-YwobsMFjOGVNqnRD5aikc429w=Xg@mail.gmail.com>
In-reply-to <1378593141.55.0.388686838068.issue18963@psf.upfronthosting.co.za>
Content
> R. David Murray added the comment:
>
> See also issue issue 17409.
>
> The code isn't setting it to RLIM_INFINITY explicitly, though, so this must mean that OSX is reporting an infinite hard limit when the hard limit is not in fact infinite.  Seems like this is an OSX bug that we will have to work around somehow.

Indeed.
I saw this while testing on "custom" buildbots, and opted for the
simplest solution: I added a @require_mac_version decorator, hoping
this would be solved in recent OSX versions. Apparently not :)

As a simple check, does the following work on OSX ?
>>> limit = resource.getrlimit(resource.RLIMIT_NOFILE)
>>> resource.setrlimit(resource.RLIMIT_NOFILE, limit)

Does the attached patch solve this?
Files
File name Uploaded
selectors_osx.diff neologix, 2013-09-08.08:37:37
History
Date User Action Args
2013-09-08 08:37:38neologixsetrecipients: + neologix, ned.deily, r.david.murray
2013-09-08 08:37:38neologixlinkissue18963 messages
2013-09-08 08:37:37neologixcreate