[issue37790] subprocess.Popen() is extremely slow

2019-08-16 Thread Alexander Pyhalov
Alexander Pyhalov added the comment: Even if I use import subprocess process = subprocess.Popen(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE

[issue37790] subprocess.Popen() is extremely slow

2019-08-16 Thread Alexander Pyhalov
Alexander Pyhalov added the comment: I couldn't reproduce entire test, as wsdiff script is rather large, but here's the simplified version. If Popen is used more often, difference is much more significant. # Using workaround $ python3.5 ~/tmp/1.py 1 10.780487537384033 # Without workaround

[issue37790] subprocess.Popen() is extremely slow

2019-08-07 Thread Alexander Pyhalov
Alexander Pyhalov added the comment: I've tried to rewrite subporcess.getstatusoutput() usage with subprocess.Popen() and switch to shell=False, it didn't help, so I doubti it getstatusoutput() overhead, it's Popen() issue. -- ___ Python tracker

[issue37790] subprocess.Popen() is extremely slow

2019-08-07 Thread Alexander Pyhalov
New submission from Alexander Pyhalov : We've moved illumos-gate wsdiff python tool from Python 2 to Python 3. The tool does the following - for each file from old and new proto area compares file attributes to find differences in binary otput (spawning elfdump, dump and other utilities

[issue23895] python socket module fails to build on Solaris when -zignore is in LDFLAGS

2015-05-28 Thread Alexander Pyhalov
Alexander Pyhalov added the comment: We have similar patch here in OpenIndiana. The patch is correct. -- nosy: +Alexander.Pyhalov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23895

[issue23895] python socket module fails to build on Solaris when -zignore is in LDFLAGS

2015-05-28 Thread Alexander Pyhalov
Alexander Pyhalov added the comment: BTW, we use the following version for Python 3.4 -- Added file: http://bugs.python.org/file39539/socket.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23895

[issue20049] string.lowercase and string.uppercase can contain garbage

2013-12-21 Thread Alexander Pyhalov
New submission from Alexander Pyhalov: When Python 2.6 (or 2.7) compiled with _XOPEN_SOURCE=600 on illumos string.lowercase and string.uppercase contain garbage when UTF-8 locale is used. (OpenIndiana bug report - https://www.illumos.org/issues/4411 ). The reason is that with UTF-8 locale

[issue20049] string.lowercase and string.uppercase can contain garbage

2013-12-21 Thread Alexander Pyhalov
Alexander Pyhalov added the comment: Honestly, I don't understand locale-related things good enough. But I received this explanation when discussed similar issue in illumos developers mailing list. http://comments.gmane.org/gmane.os.illumos.devel/14193 2013/12/22 Antoine Pitrou rep

[issue20049] string.lowercase and string.uppercase can contain garbage

2013-12-21 Thread Alexander Pyhalov
Alexander Pyhalov added the comment: I've discussed this once more. From islower man page: RETURN VALUES If the argument to any of the character handling macros is not in the domain of the function, the result is undefined. And (char)128-255 are not legal UTF-8 (at least what I