[issue9232] Allow trailing comma in any function argument list.

Larry Hastings added the comment: Moratorium's long over. Will this patch rise from the dead? -- nosy: +larry ___ Python tracker ___ _

[issue22046] ZipFile.read() should mention that it might throw NotImplementedError

Changes by Serhiy Storchaka : -- stage: -> needs patch versions: +Python 3.4, Python 3.5 -Python 3.3 ___ Python tracker ___ ___ Pytho

[issue19023] ctypes docs: Unimplemented and undocumented features

Martin Panter added the comment: Here is the patch stripped of all the noise and the structure and union stuff, so you can see just the changes related to arrays and pointers. However I have not attempted to apply the patch, nor addressed Georg’s comment about the “contents” attribute. --

[issue10803] ctypes: better support of bytearray objects

Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue21907] Update Windows build batch scripts

Roundup Robot added the comment: New changeset 4c1d543135ef by Zachary Ware in branch 'default': Issue #21907: Avoid using double quotes to check argument values. http://hg.python.org/cpython/rev/4c1d543135ef -- ___ Python tracker

[issue6259] ctypes pointer arithmetic

Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue21907] Update Windows build batch scripts

Roundup Robot added the comment: New changeset 60c61ea64021 by Zachary Ware in branch 'default': Issue #21907: Further improvments to build_pgo.bat. Patch by Ingolf Becker. http://hg.python.org/cpython/rev/60c61ea64021 -- ___ Python tracker

[issue11429] ctypes is highly eclectic in its raw-memory support

eryksun added the comment: > Interesting that “cast” accepts a byte string. If this is > intended behaviour, it would be good to document that. > Currently it says it takes “an object that can be > interpreted as a pointer”. cast makes an FFI call: _cast = PYFUNCTYPE(py_object,

[issue20341] Argument Clinic: add "nullable ints"

Raymond Hettinger added the comment: Larry, ISTM that you are bulldozing your way through something that isn't an actual problem to be solved. > I can see why you'd think this was a waste of time. I don't think it is just a waste of time; I think it is a bad idea. You have a very strong no

[issue22029] argparse - CSS white-space: like control for individual text blocks

Changes by paul j3 : Removed file: http://bugs.python.org/file36160/issue22029_2.patch ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue22029] argparse - CSS white-space: like control for individual text blocks

Changes by paul j3 : Added file: http://bugs.python.org/file36187/issue22029_2.patch ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue20341] Argument Clinic: add "nullable ints"

Larry Hastings added the comment: FWIW, Martin agreed with me at EuroPython that "nullable int" is the proper name. So does Wikipedia: http://en.wikipedia.org/wiki/Nullable_type As for "repeat_new": like I said, I don't intend to check in this change when checking in nullable ints. (I

[issue20341] Argument Clinic: add "nullable ints"

Raymond Hettinger added the comment: FWIW, I agree with Antoine that Nullable Int is a misnomer. Also, I don't buy into this mission to change signatures for optional ints into int-or-none. In particular, itertools.repeat() is fine as-is. Optional int APIs have been around for a long time,

[issue22108] python c api wchar_t*/char* passing contradiction

STINNER Victor added the comment: > What I'd really like to see in CPython is that the internal storage (and the > way it's exposed in the C-API) is just raw bytes (=> char*). Python is portable, we care of Windows. On Windows, wchar_t* is the native type for strings (ex: command line, environ

[issue22117] Rewrite pytime.h to work on nanoseconds

STINNER Victor added the comment: The effective* resolution -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22117] Rewrite pytime.h to work on nanoseconds

STINNER Victor added the comment: Oh, I forgot to mention that the patch of the issue #22043 also changes _PyTimeSpec_get_time() to use clock_gettime(CLOCK_REALTIME) which has a resolution of 1 nanosecond. _PyTimeSpec_get_time() already uses GetSystemTimeAsFileTime() which has a resolution of

[issue7897] Support parametrized tests in unittest

Changes by Brian Curtin : -- nosy: -brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue7944] Use the 'with' statement in conjunction with 'open' throughout test modules

Changes by Brian Curtin : -- nosy: -brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue20056] Got deprecation warning when running test_shutil.py on Windows NT 6

Mark Lawrence added the comment: The deprecation warnings are coming from the various os calls so are nothing to do with test_shutil. I think this can be closed as "not a bug". -- nosy: +BreamoreBoy ___ Python tracker

[issue7944] Use the 'with' statement in conjunction with 'open' throughout test modules

Mark Lawrence added the comment: Following on from msg185817 I'd suggest this is closed. -- nosy: +BreamoreBoy ___ Python tracker ___ _

[issue7897] Support parametrized tests in unittest

Mark Lawrence added the comment: Is there any possibility of getting this into 3.5? If it helps I've always got time on my hands so if nothing else I could do testing on Windows 8.1. -- nosy: +BreamoreBoy, zach.ware versions: +Python 3.5 -Python 3.4 ___

[issue22043] Use a monotonic clock to compute timeouts

STINNER Victor added the comment: pytimespec.patch become too large, I splitted this patch into a new issue: issue #22117. If this issue is rejected, I will rewrite pymonotonic-2.patch to use the _PyTime_timeval structure. -- ___ Python tracker

[issue11429] ctypes is highly eclectic in its raw-memory support

Martin Panter added the comment: Interesting that “cast” accepts a byte string. If this is intended behaviour, it would be good to document that. Currently it says it takes “an object that can be interpreted as a pointer”. -- ___ Python tracker

[issue18651] test failures on KFreeBSD

Mark Lawrence added the comment: A different patch is still needed for 3.4. -- nosy: +BreamoreBoy type: -> behavior versions: +Python 3.5 -Python 3.3 ___ Python tracker ___

[issue16255] subrocess.Popen needs /bin/sh but Android only has /system/bin/sh

Antoine Pitrou added the comment: Why not simply use $SHELL? -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue22117] Rewrite pytime.h to work on nanoseconds

Changes by Antoine Pitrou : -- nosy: +belopolsky, tim.peters ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue22117] Rewrite pytime.h to work on nanoseconds

Changes by Antoine Pitrou : -- type: -> enhancement versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mai

[issue22117] Rewrite pytime.h to work on nanoseconds

New submission from STINNER Victor: To prepare Python to add support of monotonic clock in pytime.h, I propose to rewrite pytime.h to use a new _PyTimeSpec structure which has a resolution of 1 nanosecond on only work on integers. Currently, pytime.h uses a _PyTime_timeval structure which has

[issue11271] concurrent.futures.ProcessPoolExecutor.map() doesn't batch function arguments by chunks

Changes by Dan O'Reilly : Added file: http://bugs.python.org/file36185/test_mult.py ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue11271] concurrent.futures.ProcessPoolExecutor.map() doesn't batch function arguments by chunks

Changes by Dan O'Reilly : Removed file: http://bugs.python.org/file36065/test_mult.py ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue11271] concurrent.futures.ProcessPoolExecutor.map() doesn't batch function arguments by chunks

Dan O'Reilly added the comment: I've attached an updated patch based on your review comments; there's now a unit test with a non-default chunksize, the chunking algorithm is more readable, and the same code path is used no matter what chunksize is provided. I've also updated the test script to

[issue20540] Python 3.3/3.4 regression in multiprocessing manager ?

Roundup Robot added the comment: New changeset 20fd13242a45 by Antoine Pitrou in branch 'default': Simplify code in multiprocessing.Connection.send_bytes(). http://hg.python.org/cpython/rev/20fd13242a45 -- ___ Python tracker

[issue22111] Improve imaplib testsuite.

Antoine Pitrou added the comment: This is now pushed. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ _

[issue22111] Improve imaplib testsuite.

Roundup Robot added the comment: New changeset 6b2cafab7a9f by Antoine Pitrou in branch 'default': Issue #22111: Assorted cleanups in test_imaplib. Patch by Milan Oberkirch. http://hg.python.org/cpython/rev/6b2cafab7a9f -- nosy: +python-dev ___ Pytho

[issue11429] ctypes is highly eclectic in its raw-memory support

eryksun added the comment: Extending byref to support bytes and str objects sounds reasonable. Here's another workaround to pass a bytes object with an offset: from ctypes import * from ctypes.util import find_library class offset: def __init__(self, arg, offset):

[issue21859] Add Python implementation of FileIO

Changes by Serhiy Storchaka : Added file: http://bugs.python.org/file36183/pyio_fileio_5.patch ___ Python tracker ___ ___ Python-bugs-list mai

[issue21859] Add Python implementation of FileIO

Serhiy Storchaka added the comment: Next iteration of the patch addressed Victor's and Akira's comments. -- ___ Python tracker ___ ___

[issue22116] Weak reference support for C function objects

Changes by Antoine Pitrou : -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue22110] enable extra compilation warnings

Antoine Pitrou added the comment: Le 31/07/2014 13:51, Charles-François Natali a écrit : > >> >> Enabling the warnings may be a good incitation for other people to fix them >> ;) > > That was my intention... > > Can I push it, and let warnings be fixed on a case-by-case basis? +1 from me.

[issue22108] python c api wchar_t*/char* passing contradiction

Jonas Jelten added the comment: Martin, i think the most intuitive and easiest way for working with strings in C are just char arrays. Starting with the main() argv being char*, probably most programmers just go with char* and all the encoding just works. This is because contact with encoding

[issue17085] test_socket crashes the whole test suite

Charles-François Natali added the comment: Thanks for the reminder Mark. Yes, it is probably still an issue with the latest 2.7 release. There were actually two issues: - send send()/sendall() call didn't block because the test doesn't write enough data: we have since added a SOCK_MAX_SIZE cons

[issue18188] ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 with certain configure flags

Mark Lawrence added the comment: Is this still a problem with later versions of Python on this platform? -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.3 ___ Python tracker __

[issue18004] test_list.test_overflow crashes Win64

Mark Lawrence added the comment: What if anything needs to be done here? -- nosy: +BreamoreBoy ___ Python tracker ___ ___ Python-bugs-

[issue17923] test glob with trailing slash fail

Mark Lawrence added the comment: Couldn't part of the patch be simplified to:- if basename or os.path.isdir(dirname): yield pathname or have I misread it? -- nosy: +BreamoreBoy ___ Python tracker

[issue21860] Correct FileIO docstrings

Changes by Serhiy Storchaka : -- assignee: docs@python -> haypo stage: needs patch -> commit review ___ Python tracker ___ ___ Python-

[issue20540] Python 3.3/3.4 regression in multiprocessing manager ?

Serhiy Storchaka added the comment: What would you say about multi_nagle_simplify.patch, Antoine? -- ___ Python tracker ___ ___ Python

[issue17085] test_socket crashes the whole test suite

Mark Lawrence added the comment: Is this still an issue with Python 2.7.8? (I don't have 2.7 or linux to test on) -- nosy: +BreamoreBoy ___ Python tracker ___ ___

[issue1702036] Make Turtle thread-safe so it does not crash

Lita Cho added the comment: I also want to note that you can create duplicate turtles by using clone, and I am not sure why you would use multiple inheritance to draw more than 1 turtle running around. I didn't think turtle was meant to be used this way. In order to draw multiple turtles, I wo

[issue1702036] Make Turtle thread-safe so it does not crash

Lita Cho added the comment: Hey! So I have been investigating this bug, but I wanted to know is the issue the fact that korka wants to create multiple turtles or do you really want to use multiple threads with Turtle? I feel like this crash is due to Tkinter not being thread safe and I am not

[issue18142] Tests fail on Mageia Linux Cauldron x86-64 with some configure flags

Mark Lawrence added the comment: Is there anything we can do here, do we close it as "out of date" or what? -- nosy: +BreamoreBoy type: -> behavior versions: +Python 3.4, Python 3.5 -Python 3.3 ___ Python tracker

[issue15152] test_subprocess failures on awfully slow builtbots

Charles-François Natali added the comment: Closing, I haven't seen this in a while. -- resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker __

[issue19062] problems with pyshell to get userdir

Changes by Serhiy Storchaka : -- components: +Windows stage: -> test needed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue19923] OSError: [Errno 512] Unknown error 512 in test_multiprocessing

Charles-François Natali added the comment: Closing, since it's likely a kernel bug. -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker _

[issue15862] IDLE not working when due to wrong Hard Drive point of os.path.expanduser

Changes by Serhiy Storchaka : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue22116] Weak reference support for C function objects

New submission from Antoine Pitrou: Currently, it is not possible to take a weakref to a PyCFunction object. However, those objects already have full GC support, so it wouldn't be silly to add weakref support to them. (this came in the context of numba, which generates such C functions on-the-

[issue22110] enable extra compilation warnings

Charles-François Natali added the comment: > Antoine Pitrou added the comment: > > Enabling the warnings may be a good incitation for other people to fix them ;) That was my intention... Can I push it, and let warnings be fixed on a case-by-case basis? -- _

[issue22101] collections.abc.Set doesn't provide copy() method

Guido van Rossum added the comment: You need to learn when to give up. :-) I wasn't the one who added a copy() method to other containers. I personally despise almost all uses of "copying" (including the entire copy module, both deep and shallow copy functionality). I much prefer to write e.

[issue22112] '_UnixSelectorEventLoop' object has no attribute 'create_task'

Guido van Rossum added the comment: asyncio has an explicit exemption from the general rule that bugfixes should not add new features. This is because of the "provisional" status of the PEP. We'll stop doing this once 3.5 is out. I don't know what's up with the online docs. On Thu, Jul 31, 2014

[issue20170] Derby #1: Convert 137 sites to Argument Clinic in Modules/posixmodule.c

Zachary Ware added the comment: The patch applies and compiles cleanly, and I finally tracked down what was causing the errors I reported yesterday: os_utime_impl was changed to use Py_RETURN_NONE instead of just setting return_value = Py_None, so Windows skipped the exit routine and left an o

[issue22112] '_UnixSelectorEventLoop' object has no attribute 'create_task'

Daniel Greenfeld added the comment: First, if there is documentation that says, "3.4.1", doesn't it make sense that the documentation should only be for 3.4.1? Which means that this create_task documentation should be reverted in the 3.4.1 documentation to match the 3.4.1 specification. Secon

[issue22114] You cannot call communicate() safely after receiving an exception (EINTR or EAGAIN)

Amrith Kumar added the comment: r.david.murray, I guess the issue we have is that something (hypothesis: eventlet) is causing the blocking API to communicate() to throw an EAGAIN. This (https://bugs.launchpad.net/nova/+bug/1271331) is the bug that was fixed a while ago in OpenStack that introd

[issue22114] You cannot call communicate() safely after receiving an exception (EINTR or EAGAIN)

R. David Murray added the comment: By the definition of the (blocking) communicate API, communicate can only be called once (it feeds in all the input, and reads all the output). -- ___ Python tracker

[issue18402] Finding perl64

Steve Dower added the comment: At one point the version of OpenSSL on svn.python.org did not have the correct makefiles for a 64-bit Windows build, but this was resolved. You also don't need 64-bit Perl to generate these files, and the file has been renamed to "prepare_ssl.py" and appears to o

[issue22114] You cannot call communicate() safely after receiving an exception (EINTR or EAGAIN)

Amrith Kumar added the comment: haypo; no argument from me. I just updated the description to make it more exact. I may have received EINTR or EAGAIN. In either event, I need to debug some more and try and do a clean repro and then figure out a proper fix. In the meanwhile, I proposed a fix

[issue22114] You cannot call communicate() safely after receiving an exception (EINTR or EAGAIN)

Changes by Amrith Kumar : -- title: You cannot call communicate() safely after receiving EAGAIN -> You cannot call communicate() safely after receiving an exception (EINTR or EAGAIN) ___ Python tracker ___

[issue22100] Use $HOSTPYTHON when determining candidate interpreter for $PYTHON_FOR_BUILD.

Shiz added the comment: After some further investigation it seems the which-clause fails when given a relative path. Since we should expect $HOSTPYTHON to be present in the first place, I modified the patch a bit to special-case the $HOSTPYTHON check, and fall back on the other interpreters as

[issue11427] ctypes from_buffer no longer accepts bytes

eryksun added the comment: cast calls ctypes._cast(obj, obj, typ). _cast is a ctypes function pointer defined as follows: _cast = PYFUNCTYPE(py_object, c_void_p, py_object, py_object)(_cast_addr) Since cast makes an FFI call that converts the first arg to c_void_p,

[issue22114] You cannot call communicate() safely after receiving EAGAIN

STINNER Victor added the comment: > However, I submit to you that this is NOT an eventlet issue. (...) capture > all exceptions that would point a user to retry (such as EAGAIN and EINTR) > and mask them and return some EFATAL. You cannot get EAGAIN on a blocking file descriptor and subprocess

[issue22114] You cannot call communicate() safely after receiving EAGAIN

Amrith Kumar added the comment: I see three comments, one from r.david.murray, one from haypo and one from pitrou. I'll try and address all three. r.david.murray: The code in question is in https://github.com/openstack/oslo-incubator/blob/master/openstack/common/processutils.py#L177-L189 not

[issue15986] memoryview: expose 'buf' attribute

Antoine Pitrou added the comment: Le 31/07/2014 11:24, David Beazley a écrit : > > Well, a lot of things in this big bad world are dangerous. Don't see how this is any more dangerous than all of the peril that tools like ctypes and llvmpy already provide. The point of the buffer API is to make m

[issue15986] memoryview: expose 'buf' attribute

David Beazley added the comment: One of the other goals of memoryviews is to make memory access less hacky. To that end, it would be nice to have the .buf attribute available given that all of the other attributes are already there. I don't see why people should need to do some even more hac

[issue15986] memoryview: expose 'buf' attribute

David Beazley added the comment: Well, a lot of things in this big bad world are dangerous. Don't see how this is any more dangerous than all of the peril that tools like ctypes and llvmpy already provide. -- ___ Python tracker

[issue15986] memoryview: expose 'buf' attribute

Antoine Pitrou added the comment: Ha, llvmpy... Yes, it could be useful. It's dangerous too, especially since the buffer isn't necessarily contiguous. -- ___ Python tracker ___

[issue22111] Improve imaplib testsuite.

Antoine Pitrou added the comment: Thank you, Milan. The latest patch looks good to me. -- ___ Python tracker ___ ___ Python-bugs-list

[issue15986] memoryview: expose 'buf' attribute

David Beazley added the comment: There are other kinds of libraries that might want to access the .buf attribute. For example, the llvmpy extension. Exposing it would be useful. -- ___ Python tracker

[issue22114] You cannot call communicate() safely after receiving EAGAIN

STINNER Victor added the comment: Instead of just catching EAGAIN, you can catch BlockingIOError. In Python 2.7, it means catching: (EAGAIN, EALREADY, EINPROGRESS, EWOULDBLOCK) errors. I made a similar change in asyncore recently: --- changeset: 91833:d422062d7d36 branch: 2.7 parent:

[issue22114] You cannot call communicate() safely after receiving EAGAIN

Antoine Pitrou added the comment: This sounds like an issue specific to eventlet. There's no reason for the standard communicate() call to raise EAGAIN, since the created pipes are blocking. That said, if the fix is that trivial, I wouldn't be opposed to see it enter the stdlib (assuming it d

[issue15381] Optimize BytesIO to do less reallocations when written, similarly to StringIO

Serhiy Storchaka added the comment: Synchronized with tip. Unfortunately there are no common points with recent issue22003 changes so they should be reverted (except tests). -- versions: +Python 3.5 -Python 3.4 Added file: http://bugs.python.org/file36180/bytesio_resized_bytes-4.patch

[issue15986] memoryview: expose 'buf' attribute

Antoine Pitrou added the comment: ctypes could grow a way to access the Py_buffer API instead. -- nosy: +amaury.forgeotdarc, belopolsky, meador.inge, pitrou ___ Python tracker __

[issue15381] Optimize BytesIO to do less reallocations when written, similarly to StringIO

Changes by Serhiy Storchaka : -- nosy: +benjamin.peterson, dw, hynek, kmike, python-dev, scoder, skrah, stutzbach ___ Python tracker ___ _

[issue22085] Drop support of Tk 8.3

Serhiy Storchaka added the comment: I close this issue because don't want to change topic yet once (and one feature per issue). Separate issue22115 was opened for adding new trace methods. -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed __

[issue22108] python c api wchar_t*/char* passing contradiction

Zachary Ware added the comment: See also issue20466 (which has a patch for this, but I cannot speak for its effectiveness). I'd be in favor of closing that issue and this one as duplicates of #18395, and noting in #18395 that the embedding example must be updated before that issue is closed.

[issue22115] Add new methods to trace Tkinter variables

New submission from Serhiy Storchaka: Command used to monitor Tcl variable access ("trace variable", "trace vdelete", "trace vinfo") are deprecated and will likely be removed in a future version of Tcl. Replacements ("trace add variable", "trace remove variable", "trace info variable") use sli

[issue22114] You cannot call communicate() safely after receiving EAGAIN

R. David Murray added the comment: I believe our recent thinking in recent times has been to handle EAGAIN in the higher level interfaces such as subprocess, not expose them to the caller. Does python3 have the same problem? I isn't clear that you have provided enough information to reproduce

[issue22111] Improve imaplib testsuite.

Milan Oberkirch added the comment: AntoinePitrou: Thanks for the review! I made the suggested changes and could not resist refactoring the hole thing (since I plan to spend some time on that file I wanted it to be readable and pep conform). -- Added file: http://bugs.python.org/file361

[issue22101] collections.abc.Set doesn't provide copy() method

Akira Li added the comment: > I don't think this is needed nor do I think that it is a good idea to > have a copy() method in the ABCs because they know so little about > their concrete underlying class (perhaps the backing store in the > filesystem or a database). Besides, a user already has wo

[issue18597] On Windows sys.stdin.readline() doesn't handle Ctrl-C properly

Drekin added the comment: Shouldn't there be a Ctrl-C check in Modules/_io/fileio.c:fileio_read* functions? I think some of these are called by standard sys.stdin.readline(). -- ___ Python tracker

[issue17371] Mismatch between Python 3.3 build environment and distutils compiler support

Martin v. Löwis added the comment: Installing VS 2010 express was indeed the right solution. -- resolution: -> not a bug status: open -> closed ___ Python tracker ___ __

[issue22108] python c api wchar_t*/char* passing contradiction

Martin v. Löwis added the comment: Jonas, why do you say that? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue22114] You cannot call communicate() safely after receiving EAGAIN

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue22114] You cannot call communicate() safely after receiving EAGAIN

Amrith Kumar added the comment: I'll supply a patch for this proposed change. -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue22114] You cannot call communicate() safely after receiving EAGAIN

New submission from Amrith Kumar: Environment: - Linux (Ubuntu 14.04 LTS, x64) running Python 2.7. - Code uses eventlet.green.subprocess Code establishes subprocess as: subprocess.Popen(command, stdin=subprocess.PIPE, stdout=subprocess.PIPE,

[issue17620] Python interactive console doesn't use sys.stdin for input

Drekin added the comment: Sorry for formating in the previous message. Repeating… I looked to the sourcecode and found the following. First, the codepath of how interactive loop gets its input follows: Python/pythonrun.c:PyRun_InteractiveLoopFlags Python/pythonrun.c:PyRun_InteractiveOneObject P

[issue17620] Python interactive console doesn't use sys.stdin for input

Drekin added the comment: I looked to the sourcecode and found the following. First, the codepath of how interactive loop gets its input follows: Python/pythonrun.c:PyRun_InteractiveLoopFlags Python/pythonrun.c:PyRun_InteractiveOneObject Python/pythonrun.c:PyParser_ASTFromFileObject Parse/parset

[issue11427] ctypes from_buffer no longer accepts bytes

Martin Panter added the comment: For the record, I have been (ab?)using the “c_char_p” type to get the address of immutable byte strings without copying memory: >>> from ctypes import * >>> data = b"123\x00abc" >>> pubyte = cast(c_char_p(data), POINTER(c_ubyte)) >>> address = addressof(pubyte.c

[issue15986] memoryview: expose 'buf' attribute

Martin Panter added the comment: This issue was linked from . I was looking for ways to pass read-only memory views into “ctypes” without copying memory, and came across that thread. Assuming this “buf” attribute points

[issue22043] Use a monotonic clock to compute timeouts

STINNER Victor added the comment: Oh, pymonotonic-2.patch didn't get its "review" link because it depends on pytimespec.patch which is not merged yet. -- ___ Python tracker ___

[issue22043] Use a monotonic clock to compute timeouts

STINNER Victor added the comment: pytimespec.patch removes *private* functions which were exposed in the stable ABI: - _PyTime_gettimeofday() - _PyTime_gettimeofday_info() It also removes private macros: - _PyTime_ADD_SECONDS() - _PyTime_INTERVAL() In pymonotonic.patch, I reused the same nam

[issue12312] is ok

Missy Gomrz added the comment: Re: is ol missy orr -- nosy: +Missy.Gomrz ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue22043] Use a monotonic clock to compute timeouts

Changes by STINNER Victor : Added file: http://bugs.python.org/file36177/pymonotonic-2.patch ___ Python tracker ___ ___ Python-bugs-list maili

  1   2   >