René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add more RLIMIT_* constants","articleBody":"# Feature or enhancement\n\nThere are some `RLIMIT_*` constants on Posix platforms which are not currently exposed in the `resource` module.\n\n* `RLIMIT_NTHR`. Available on NetBSD \u003e= 7.0, QNX \u003e= 6.3.2.\n* `RLIMIT_UMTXP`. Available on FreeBSD \u003e= 11.\n* `RLIMIT_PIPEBUF`. Available in the main branch on FreeBSD ~(\u003e= 15?)~ \u003e= 14.2.\n* `RLIMIT_THREADS`. Available on AIX. The same as `RLIMIT_NTHR`?\n* `RLIMIT_VMEM`. Available on Solaris/OpenIndiana. On FreeBSD \u003e= 5.3 it is an alias of `RLIMIT_AS`.\n\nConstants `RLIM_SAVED_CUR` and `RLIM_SAVED_MAX` are used on some platforms (Solaris/OpenIndiana, AIX) to represent values that cannot be represented in 32-bit `rlim_t`.\n\n~It is perhaps too early to add `RLIMIT_PIPEBUF`.~\n\n`RLIMIT_NTHR` and `RLIMIT_THREADS`, should we only add one of them on the corresponding platform or add both names as aliases of one other?\n\n`RLIMIT_VMEM`. Should we add it as an alias of `RLIMIT_AS` on all other platforms?\n\nI am not sure whether `RLIM_SAVED_CUR` and `RLIM_SAVED_MAX` are still relevant on modern Unixes. Their use is complicated. They are the part of Posix, but not defined on Linux. On FreeBSD they are aliases of `RLIM_INFINITY` and are not useful at all.\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-137513\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/serhiy-storchaka","@type":"Person","name":"serhiy-storchaka"},"datePublished":"2025-08-07T11:11:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/137512/cpython/issues/137512"}