[issue47169] Stable ABI: Some optional (#ifdef'd) functions aren't handled correctly

Jakub Kulik added the comment: Solaris is affected by missing `PyThread_get_thread_native_id`; all other symbols from the SYMBOL_NAMES tuple (in test_stable_abi_ctypes.py) are available. -- ___ Python tracker <https://bugs.python.org/issue47

[issue47169] Stable ABI: Some optional (#ifdef'd) functions aren't handled correctly

Change by Jakub Kulik : -- nosy: +kulikjak ___ Python tracker <https://bugs.python.org/issue47169> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44133] Some C-API symbols (e.g. Py_FrozenMain) are not always exported on Unix

Jakub Kulik added the comment: Yes, it still does, and PyThread_get_thread_native_id is the only symbol missing. -- ___ Python tracker <https://bugs.python.org/issue44

[issue47058] Skip tests failing on Solaris

Change by Jakub Kulik : -- title: Skip tests failing on Solaris worker -> Skip tests failing on Solaris ___ Python tracker <https://bugs.python.org/issu

[issue47058] Skip tests failing on Solaris worker

Change by Jakub Kulik : -- keywords: +patch pull_requests: +30068 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31978 ___ Python tracker <https://bugs.python.org/issu

[issue47058] Skip tests failing on Solaris worker

New submission from Jakub Kulik : There are several tests failing on the recently added Solaris buildbot worker. This Issue aims to fix/skip the to make Solaris green on buildbot. ## test_posix ## Issues with the `os.sched_get_priority_min`; fix offered here

[issue44133] Some C-API symbols (e.g. Py_FrozenMain) are not always exported on Unix

Jakub Kulik added the comment: Ah, sorry, I could have described the issue better. It's not a problem with exporting, PyThread_get_thread_native_id() isn't available on Solaris (and possibly other platforms) at all. https://github.com/python/cpython/blob/main/Include/pythread.h#L28 https

[issue40066] Enum: modify __repr__, __str__; update docs

Jakub Kulik added the comment: This also broke our Solaris build with the following error: == FAIL: testGetaddrinfo (test.test_socket.GeneralModuleTests

[issue44133] Some C-API symbols (e.g. Py_FrozenMain) are not always exported on Unix

Jakub Kulik added the comment: >> On Solaris (and most likely several other platforms), >> `PyThread_get_thread_native_id` is also not available. > Oh, I added an explicit test for that in my PR 30556. Now it started failing on a

[issue46099] Solaris: Fix pthread_getcpuclockid test

Change by Jakub Kulik : -- keywords: +patch pull_requests: +28358 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30140 ___ Python tracker <https://bugs.python.org/issu

[issue46099] Solaris: Fix pthread_getcpuclockid test

New submission from Jakub Kulik : On Solaris, when `pthread_getcpuclockid()` is called with current thread id as an argument, it returns `CLOCK_THREAD_CPUTIME_ID`. == FAIL: test_pthread_getcpuclockid

[issue44133] Some C-API symbols (e.g. Py_FrozenMain) are not always exported

Jakub Kulik added the comment: On Solaris (and most likely several other platforms), `PyThread_get_thread_native_id` is also not available. -- nosy: +kulikjak ___ Python tracker <https://bugs.python.org/issue44

[issue44935] Solaris: enable posix_spawn in subprocess

Change by Jakub Kulik : -- keywords: +patch pull_requests: +26264 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27795 ___ Python tracker <https://bugs.python.org/issu

[issue44935] Solaris: enable posix_spawn in subprocess

New submission from Jakub Kulik : Solaris also provides posix_spawn() syscall that can/should be used in the subprocess module to spawn new processes. -- components: Library (Lib) messages: 399750 nosy: kulikjak priority: normal severity: normal status: open title: Solaris: enable

[issue43498] "dictionary changed size during iteration" error in _ExecutorManagerThread

Jakub Kulik added the comment: I think that even if copy() doesn't fix it entirely, it's still much better than nothing. I never encountered the issue mentioned in bpo-40327, but I saw this issue several times a week (before applying the proposed patch

[issue43219] shutil.copy raises IsADirectoryError when the directory does not actually exist

Change by Jakub Kulik : -- pull_requests: +25802 pull_request: https://github.com/python/cpython/pull/27257 ___ Python tracker <https://bugs.python.org/issue43

[issue43219] shutil.copy raises IsADirectoryError when the directory does not actually exist

Jakub Kulik added the comment: On Solaris (I checked this on Oracle and SmartOS), the error is: NotADirectoryError: [Errno 20] Not a directory: 'not_a_dir/' which I think belongs to the 'errors are not confusing' category with Windows and macOS. -- nosy: +kulikjak

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Change by Jakub Kulik : -- pull_requests: +24998 pull_request: https://github.com/python/cpython/pull/26405 ___ Python tracker <https://bugs.python.org/issue43

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Jakub Kulik added the comment: Sorry for delayed response. Considering that we are not delivering or using 3.8 in any way and this issue doesn't seem to impact anybody else, we can omit the backport to 3.8. I will prepare another PR with a news fragment, and after that, this can

[issue41843] Reenable sendfile in shutil.copyfile() on Solaris

Jakub Kulik added the comment: Based on the comment https://bugs.python.org/issue43743#msg393429 I think my question is answered: #36610 should not be reverted. Attached PR (which merely adds Solaris to systems where _USE_CP_SENDFILE is True) should thus be the preferred way of reenabling

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Change by Jakub Kulik : -- components: +Unicode -Tests versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.11 ___ Python tracker <https://bugs.python.org/issue43

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Change by Jakub Kulik : -- pull_requests: +24530 pull_request: https://github.com/python/cpython/pull/25847 ___ Python tracker <https://bugs.python.org/issue43

[issue43498] "dictionary changed size during iteration" error in _ExecutorManagerThread

Jakub Kulik added the comment: I investigated a little bit more and found out that this happens when `ProcessPoolExecutor::_adjust_process_count()` adds a new process during the iteration. With the following change, I can reproduce this reliably every time: --- Python-3.9.1/Lib/concurrent

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Jakub Kulik added the comment: I forgot to mention: this affects Oracle Solaris. I tested this on SmartOS, and I cannot reproduce it there as it seems that they are using Unicode representation for all locales. Based on the documentation, this might also affect other systems as well (e.g

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Change by Jakub Kulik : -- keywords: +patch pull_requests: +23840 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25096 ___ Python tracker <https://bugs.python.org/issu

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

New submission from Jakub Kulik : On Linux, wchar_t values are mapped to their UTF-8 counterparts; however, that does not have to be the case as the standard allows any arbitrary representation to be used, and this is the case for Solaris. In Oracle Solaris, the internal form of wchar_t

[issue43498] "dictionary changed size during iteration" error in _ExecutorManagerThread

Change by Jakub Kulik : -- keywords: +patch pull_requests: +23630 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24868 ___ Python tracker <https://bugs.python.org/issu

[issue43498] "dictionary changed size during iteration" error in _ExecutorManagerThread

New submission from Jakub Kulik : Recently several of our Python 3.9 builds froze during `make install` with the following trace in logs: Listing .../components/python/python39/build/prototype/sparc/usr/lib/python3.9/lib2to3/tests/data/fixers/myfixes... Exception in thread Thread-1

[issue41843] Reenable sendfile in shutil.copyfile() on Solaris

Change by Jakub Kulik : -- keywords: +patch pull_requests: +22748 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23893 ___ Python tracker <https://bugs.python.org/issu

[issue19561] request to reopen Issue837046 - pyport.h redeclares gethostname() if SOLARIS is defined

Change by Jakub Kulik : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 2.7, Python 3.3 ___ Python tracker <https://bugs.python.org/issue19561> ___ ___

[issue37232] Parallel compilation fails because of low ulimit.

Jakub Kulik added the comment: I am closing this as it is true that the limit on files of 256 is pretty low, and no matter how robust you make it, arbitrarily low ulimits will crash it anyway. -- resolution: -> not a bug stage: -> resolved status: open -&g

[issue42277] Solaris & PEP 3149: start using ABI version tagged .so files

Change by Jakub Kulik : -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue42277] Solaris & PEP 3149: start using ABI version tagged .so files

Jakub Kulik added the comment: This was resolved with issue 42604 and PR 23708. -- ___ Python tracker <https://bugs.python.org/issue42277> ___ ___ Python-bug

[issue42655] Fix subprocess extra_groups gid conversion

Jakub Kulik added the comment: I checked and indeed there seems to be no reason as for why should we use `void *` rather than `gid_t *` and `uid_t *`. I changed that in the attached PR. -- ___ Python tracker <https://bugs.python.org/issue42

[issue42655] Fix subprocess extra_groups gid conversion

Change by Jakub Kulik : -- keywords: +patch pull_requests: +22655 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23762 ___ Python tracker <https://bugs.python.org/issu

[issue42655] Fix subprocess extra_groups gid conversion

New submission from Jakub Kulik : C function `subprocess_fork_exec` incorrectly transforms gids from the `extra_groups` argument because it passes `unsigned long*` rather than `pid_t*` into the `_Py_Gid_Converter()`. Assuming that `gid_t` is 32 bit and `unsigned long` is 64 bit (which

[issue41818] Lib/pty.py major revision

Jakub Kulik added the comment: This change also broke Solaris (SunOS), where (similarly to BSDs and Darwin) OSError is not raised in the `new test_master_read()` test. Adding `or PLATFORM == "SunOS"` into the `expectedFailureOnBSD` function fixes this issue, but it's no longer

[issue19561] request to reopen Issue837046 - pyport.h redeclares gethostname() if SOLARIS is defined

Change by Jakub Kulik : -- pull_requests: +22106 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23208 ___ Python tracker <https://bugs.python.org/issu

[issue19561] request to reopen Issue837046 - pyport.h redeclares gethostname() if SOLARIS is defined

Jakub Kulik added the comment: And for the reference, Solaris distros are already removing this code: https://github.com/oracle/solaris-userland/blob/master/components/python/python37/patches/15-gethostname.patch https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/python

[issue19561] request to reopen Issue837046 - pyport.h redeclares gethostname() if SOLARIS is defined

Jakub Kulik added the comment: I think this code should be removed. It was added in its current form more than 20 years ago with the intention to add function declarations missing from system include files: https://github.com/python/cpython/commit/1e0c2f4bee43728930bd5f4dc77283f09c4ba004

[issue41839] Solaris: Fix error checking in sched_get_priority_ functions

Jakub Kulik added the comment: > Checking for -1 rather than all negative values fixes this issue. To be 100% exact, it should be "checking for -1 and errno" (as other Jakub noted in the PR). Here is the standard for reference: https://pubs.opengroup.org/onlinepubs/009695

[issue42277] Solaris & PEP 3149: start using ABI version tagged .so files

Change by Jakub Kulik : -- keywords: +patch pull_requests: +22088 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23182 ___ Python tracker <https://bugs.python.org/issu

[issue42277] Solaris & PEP 3149: start using ABI version tagged .so files

New submission from Jakub Kulik : Solaris doesn't have ABI version tagged .so files enabled in upstream CPython yet, but almost every Solaris distribution* patches this functionality in: Oracle Solaris: https://github.com/oracle/solaris-userland/blob/master/components/python/python39/patches

[issue42237] test_socket.SendfileUsingSendfileTest fails on illumos

Change by Jakub Kulik : -- versions: +Python 3.9 ___ Python tracker <https://bugs.python.org/issue42237> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42237] test_socket.SendfileUsingSendfileTest fails on illumos

Jakub Kulik added the comment: I did some further digging, and this is indeed not possible on Oracle Solaris (that is, sendfile() cannot write bytes and fail during the same call). We considered this a bug and changed/fixed it several years ago. Manual page doesn't mention that either

[issue35455] Solaris: thread_time doesn't work with current implementation

Change by Jakub Kulik : -- versions: -Python 3.7 ___ Python tracker <https://bugs.python.org/issue35455> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35455] Solaris: thread_time doesn't work with current implementation

Change by Jakub Kulik : -- pull_requests: +22057 pull_request: https://github.com/python/cpython/pull/23145 ___ Python tracker <https://bugs.python.org/issue35

[issue35455] Solaris: thread_time doesn't work with current implementation

Change by Jakub Kulik : -- versions: +Python 3.10 ___ Python tracker <https://bugs.python.org/issue35455> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35455] Solaris: thread_time doesn't work with current implementation

Change by Jakub Kulik : -- title: Solaris thread_time doesn't work with current implementation -> Solaris: thread_time doesn't work with current implementation ___ Python tracker <https://bugs.python.org/issu

[issue35455] Solaris thread_time doesn't work with current implementation

Jakub Kulik added the comment: Comment from https://bugs.python.org/issue42173#msg380205 confirmed that this issue is still relevant to Illumos based systems. Because of that, I am happy to resolve it. -- ___ Python tracker <ht

[issue42173] Drop Solaris support

Jakub Kulik added the comment: Thanks Andy, good to know we are seeing the same issue! We tried to fix sendfile differences in Python code before as well, but as you said, it was never 100% solved. Recently we finally fixed it in C and it was accepted (https://bugs.python.org/issue41687

[issue42173] Drop Solaris support

Jakub Kulik added the comment: I ran the test and the results are attached (the first one is a complete test and the other one failed tests in verbose mode). I checked the failing tests and divided them into several groups: issues already reported: test_asyncio - reported and being solved

[issue42173] Drop Solaris support

Change by Jakub Kulik : Added file: https://bugs.python.org/file49559/Oracle_Solaris_detailed_test.txt ___ Python tracker <https://bugs.python.org/issue42173> ___ ___

[issue42173] Drop Solaris support

Jakub Kulik added the comment: Hi, here I am passing on several notes from the Oracle Solaris team: - Oracle continues to develop and advance Oracle Solaris technology, and have committed to doing so for years to come. We release a new update (so called SRU) every month (https

[issue27777] cgi.FieldStorage can't parse simple body with Content-Length and no Content-Disposition

Jakub Kulik added the comment: We internally tested the most recent PR and found some issues with it: https://github.com/python/cpython/pull/21457#issuecomment-698845895 We ended up using a much simpler patch, which seems to work as expected. --- Python-3.7.8/Lib/cgi.py +++ Python-3.7.8/Lib

[issue41843] Reenable sendfile in shutil.copyfile() on Solaris

New submission from Jakub Kulik : The use of sendfile() in shutil.copyfile() on Solaris was previously disabled in #36610 due to slightly different behavior. This difference was recently accounted for in #41687, and I observed no other unexpected problems/differences with sendfile. Can we

[issue41839] Fix error checking in sched_get_priority_ functions

Change by Jakub Kulik : -- versions: +Python 3.8 ___ Python tracker <https://bugs.python.org/issue41839> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41839] Fix error checking in sched_get_priority_ functions

Change by Jakub Kulik : -- keywords: +patch pull_requests: +21413 stage: -> patch review pull_request: https://github.com/python/cpython/pull/22374 ___ Python tracker <https://bugs.python.org/issu

[issue41839] Fix error checking in sched_get_priority_ functions

New submission from Jakub Kulik : Python presumes that any negative number returned from sched_get_priority_min or sched_get_priority_max indicates that error has occurred. However, neither Linux manual pages nor POSIX.1-2001 specification forbids negative values to be returned; only -1 has

[issue35520] Python won't build with dtrace enabled on some systems.

Jakub Kulik added the comment: No more non-security related backports to 3.7 allowed. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue41687] sendfile implementation is not compatible with Solaris

Jakub Kulik added the comment: I just realized that the recently merged PR has broken error handling, so I opened another one with a followup fix. -- ___ Python tracker <https://bugs.python.org/issue41

[issue41687] sendfile implementation is not compatible with Solaris

Change by Jakub Kulik : -- pull_requests: +21209 pull_request: https://github.com/python/cpython/pull/22128 ___ Python tracker <https://bugs.python.org/issue41

[issue33802] Regression in logging configuration

Change by Jakub Kulik : -- nosy: -kulikjak ___ Python tracker <https://bugs.python.org/issue33802> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36533] logging regression with threading + fork are mixed in 3.7.1rc2 (deadlock potential)

Change by Jakub Kulik : -- nosy: -kulikjak ___ Python tracker <https://bugs.python.org/issue36533> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33802] Regression in logging configuration

Change by Jakub Kulik : -- pull_requests: -21199 ___ Python tracker <https://bugs.python.org/issue33802> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36533] logging regression with threading + fork are mixed in 3.7.1rc2 (deadlock potential)

Change by Jakub Kulik : -- pull_requests: -21198 ___ Python tracker <https://bugs.python.org/issue36533> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6721] Locks in the standard library should be sanitized on fork

Change by Jakub Kulik : -- pull_requests: -21197 ___ Python tracker <https://bugs.python.org/issue6721> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6721] Locks in the standard library should be sanitized on fork

Change by Jakub Kulik : -- nosy: -kulikjak ___ Python tracker <https://bugs.python.org/issue6721> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33802] Regression in logging configuration

Change by Jakub Kulik : -- nosy: +kulikjak nosy_count: 7.0 -> 8.0 pull_requests: +21199 pull_request: https://github.com/python/cpython/pull/22040 ___ Python tracker <https://bugs.python.org/issu

[issue36533] logging regression with threading + fork are mixed in 3.7.1rc2 (deadlock potential)

Change by Jakub Kulik : -- nosy: +kulikjak nosy_count: 7.0 -> 8.0 pull_requests: +21198 pull_request: https://github.com/python/cpython/pull/22040 ___ Python tracker <https://bugs.python.org/issu

[issue6721] Locks in the standard library should be sanitized on fork

Change by Jakub Kulik : -- nosy: +kulikjak nosy_count: 27.0 -> 28.0 pull_requests: +21197 pull_request: https://github.com/python/cpython/pull/22040 ___ Python tracker <https://bugs.python.org/iss

[issue41687] sendfile implementation is not compatible with Solaris

Change by Jakub Kulik : -- keywords: +patch pull_requests: +21137 stage: -> patch review pull_request: https://github.com/python/cpython/pull/22040 ___ Python tracker <https://bugs.python.org/issu

[issue41687] sendfile implementation is not compatible with Solaris

New submission from Jakub Kulik : Hi, Sendfile on Solaris raises EINVAL if offset is equal or bigger than the size of the file. This is different from Linux, where similar sendfile call returns 0, which is used in an ad-hoc fashion to indicate EOF. Since Python sendfile implementation

[issue37573] asyncio: freeze when using MultiLoopChildWatcher on Solaris

Jakub Kulik added the comment: You are right, that seems to be the same issue. Thanks for closing this. -- ___ Python tracker <https://bugs.python.org/issue37

[issue35455] Solaris thread_time doesn't work with current implementation

Jakub Kulik added the comment: Correction: looking at the PR, I made it so that it checks for SunOS, so even with CLOCK_THREAD_CPUTIME_ID available, new code would be executed. So if you believe that this should be implemented for other SunOSes, I can do

[issue35455] Solaris thread_time doesn't work with current implementation

Jakub Kulik added the comment: I was speaking for Oracle Solaris 11.4, where CLOCK_THREAD_CPUTIME_ID is now implemented (and we don't need it in older releases). But you are right that other Solaris/SunOS versions might not have this and hence would find this useful. I can rebase

[issue38110] Use fdwalk() within os.closerange() impl if available

Change by Jakub Kulik : -- keywords: +patch pull_requests: +15581 pull_request: https://github.com/python/cpython/pull/15224 ___ Python tracker <https://bugs.python.org/issue38

[issue37785] argparse uses %s in gettext calls causing xgettext warnings

Jakub Kulik added the comment: Thanks, I see; this is not a change for security only stage. I merged your suggestion. -- ___ Python tracker <https://bugs.python.org/issue37

[issue35484] Segmentation fault due to faulthandler on Solaris

Jakub Kulik added the comment: Oh, thanks for the catch, it most likely is. -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue37785] argparse uses %s in gettext calls causing xgettext warnings

Change by Jakub Kulik : -- keywords: +patch pull_requests: +14894 stage: -> patch review pull_request: https://github.com/python/cpython/pull/15161 ___ Python tracker <https://bugs.python.org/issu

[issue37785] argparse uses %s in gettext calls causing xgettext warnings

Change by Jakub Kulik : -- title: argparse uses %s in gettext calls -> argparse uses %s in gettext calls causing xgettext warnings ___ Python tracker <https://bugs.python.org/issu

[issue37785] argparse uses %s in gettext calls

New submission from Jakub Kulik : Running xgettext on argparse.py (of any currently supported Python 3.x) return following warning: ./Lib/argparse.py: warning: 'msgid' format string with unnamed arguments cannot be properly localized: The translator cannot reorder the arguments. Please

[issue37573] asyncio: freeze when using MultiLoopChildWatcher on Solaris

New submission from Jakub Kulik : Hi, since the 3.8.0b2 test_asyncio freezes in test_subprocess when MultiLoopChildWatcher is being used as a watcher (new in b2). All other watchers are working as expected. This is all on Solaris. I tried to find out the reason for these issues and it seems

[issue37558] Shared memory tests are failing due to double slashes

Change by Jakub Kulik : -- keywords: +patch pull_requests: +14502 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14703 ___ Python tracker <https://bugs.python.org/issu

[issue37558] Shared memory tests are failing due to double slashes

New submission from Jakub Kulik : Hi, with the addition of shared memory into Python 3.8, we now have three tests failing on Solaris, namely `test_multiprocessing_fork`, `test_multiprocessing_forkserver` and `test_multiprocessing_spawn`. All of them fail in the same way

[issue37335] Improve encoding alias handling in locale coercion tests

Change by Jakub Kulik : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue37335] Improve encoding alias handling in locale coercion tests

Change by Jakub Kulik : -- pull_requests: +14265 pull_request: https://github.com/python/cpython/pull/14449 ___ Python tracker <https://bugs.python.org/issue37

[issue37335] Improve encoding alias handling in locale coercion tests

Change by Jakub Kulik : -- pull_requests: +14263 pull_request: https://github.com/python/cpython/pull/14447 ___ Python tracker <https://bugs.python.org/issue37

[issue37335] Improve encoding alias handling in locale coercion tests

Jakub Kulik added the comment: Python 3.8+ encodings are always normalized and thus no output variations handling is necessary (the code is no longer necessary). Python 3.7 (and possibly lower) can have variations in encodings - that should be fixed with codecs.lookup functions

[issue37335] Fix unexpected ASCII aliases in locale coercion tests.

Change by Jakub Kulik : -- pull_requests: +14259 pull_request: https://github.com/python/cpython/pull/14443 ___ Python tracker <https://bugs.python.org/issue37

[issue37335] Fix unexpected ASCII aliases in locale coercion tests.

Change by Jakub Kulik : -- title: Add 646 ASCII alias to locale coercion tests. -> Fix unexpected ASCII aliases in locale coercion tests. ___ Python tracker <https://bugs.python.org/issu

[issue37335] Add 646 ASCII alias to locale coercion tests.

Jakub Kulik added the comment: I just added that in the way it was already there but I see why the current solution is not the best. Also I wanted to push this into 3.7 only as this problem is not present in 3.8 (as discussed in the PR 11195 opened incorrectly against the master). Just

[issue37335] Add 646 ASCII alias to locale coercion tests.

Change by Jakub Kulik : -- pull_requests: +14107 pull_request: https://github.com/python/cpython/pull/14285 ___ Python tracker <https://bugs.python.org/issue37

[issue35455] Solaris thread_time doesn't work with current implementation

Jakub Kulik added the comment: Since I created this pull request, clock_gettime(CLOCK_THREAD_CPUTIME_ID, ..) was implemented into the Solaris kernel, so I guess that this is no longer relevant. -- resolution: -> not a bug stage: patch review -> resolved status: open -&g

[issue37335] Add 646 ASCII alias to locale coercion tests.

Change by Jakub Kulik : -- keywords: +patch pull_requests: +14063 stage: -> patch review pull_request: https://github.com/python/cpython/pull/11195 ___ Python tracker <https://bugs.python.org/issu

[issue37335] Add 646 ASCII alias to locale coercion tests.

New submission from Jakub Kulik : Locale coercion tests on Solaris are failing because 646 ASCII alias is not recognized. Its addition into the _handle_output_variations function fixes this problem. This was changed/fixed in Python 3.8 and later, where aliases are correctly translated

[issue37252] devpoll test failures on Solaris

Change by Jakub Kulik : -- keywords: +patch pull_requests: +13882 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14017 ___ Python tracker <https://bugs.python.org/issu

[issue37252] devpoll test failures on Solaris

New submission from Jakub Kulik : test_devpoll currently ends with two failures with Python 3.8 on Solaris. First one is wrong number of arguments to devpoll.register function (which thrown the same error as expected in 3.7 but now acts differently). Second one is that register and modify

[issue37232] Parallel compilation fails because of low ulimit.

Jakub Kulik added the comment: I am not sure what you are asking now. compileall with -j0 does compile on all cores simultaneously right? -- ___ Python tracker <https://bugs.python.org/issue37

[issue37232] Parallel compilation fails because of low ulimit.

Jakub Kulik added the comment: We have a limit of 256 opened files, which is not much, but I can up it and then it doesn't happen. Mainly, I wanted to report that this might be happening now. But I guess not many people will face this problem

  1   2   >