[issue24450] Add gi_yieldfrom calculated property to generator object
Changes by Yury Selivanov yseliva...@gmail.com: -- nosy: +arigo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24450 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23496] Steps for Android Native Build of Python 3.4.2
Cyd Haselton added the comment: Update: Now that I;ve finished porting a much-needed gdb to my device, I should have time to tackle patch and testing this weekend. Will post results when I have them. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23496 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24450] Add gi_yieldfrom calculated property to generator object
Armin Rigo added the comment: No problem from PyPy. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24450 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24400] Awaitable ABC incompatible with functools.singledispatch
Changes by Yury Selivanov yseliva...@gmail.com: Added file: http://bugs.python.org/file39722/corotype.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24400 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23255] SimpleHTTPRequestHandler refactor for more extensible usage.
Ned Deily added the comment: Ent, thanks for all your work on this, and thanks to Demian and Martin for their reviews. In the meantime, the Python 3.5 release cycle has reached feature code cutoff so, at this point, generally only bug fixes are being accepted into 3.5, which means this refactoring will likely land in 3.6. The next step is for a core developer to do a final review and then decide whether to commit it. Berker has been commenting on this issue so perhaps he will have time to handle it as 3.6 gets underway. (http is one of the modules/packages in the standard library where currently no core developer has volunteered to be its expert so we all share responsibility for it as time and interest permits. https://docs.python.org/devguide/experts.html) -- keywords: +needs review nosy: +ned.deily versions: +Python 3.6 -Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23255 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24419] In argparse action append_const doesn't work for positional arguments
py.user added the comment: paul j3 wrote: What are you trying to accomplish in the examples with a 'dest'? To append all that constants to one list. From this: Namespace(bar=[43], foo=[42]) To this: Namespace(x=[43, 42]) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24419 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24421] Race condition compiling Modules/_math.c
Martin Panter added the comment: Here is a hacky patch that adds #include _math.c so that it is not compiled as a separate object file. This was suggested by Mark in Issue 7518. It is far from a perfect solution, but I cannot suggest anything better without knowing more about Python’s build system. -- keywords: +patch stage: - patch review Added file: http://bugs.python.org/file39724/include-math.c.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24421 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24419] In argparse action append_const doesn't work for positional arguments
paul j3 added the comment: What are you trying to accomplish in the examples with a 'dest'? For a positional, 'dest' is derived from the 'foo' name. There is no need to supply 'dest', in fact produces the error you get. It has nothing to with this action type (as your last example demonstrates). Your case with 'foo' and 'bar' shows that 'append_const' works fine. But be ware that such an action does not make much sense for a positional. Such an action takes no arguments, i.e. 'nargs=0'. So such a positional is always present, since it does not consume any `argv` strings. You might even get an error if you supply a string. (same would be true of 'store_true' and related actions). -- nosy: +paul.j3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24419 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24419] In argparse action append_const doesn't work for positional arguments
py.user added the comment: paul j3 wrote: The name (and hence the 'dest') must be unique. The problem is in the dest argument of add_argument(). Why user can't set a custom name for a positional? We can use this list not only for positionals but for optionals too. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24419 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24419] In argparse action append_const doesn't work for positional arguments
paul j3 added the comment: None of the `append` actions makes sense with positionals. The name (and hence the 'dest') must be unique. And positionals can't be repeated. There are other ways to put a pair of values in the Namespace. For example, after parsing args.x = [42, 43] or before ns = argparse.Namespace(x=[42,43]) parser.parse_args(namespace=ns) or the `const` (or better the default) could be `[42, 43]`. Plain `append` might let you put `[42,43]` in the dest via the default, and then append further values to that list (from the user). I'd have to test that. It might be instructive to look at the `test_argparse.py` file, and search for test cases that use `append` or `const`. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24419 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24450] Add gi_yieldfrom calculated property to generator object
Changes by Yury Selivanov yseliva...@gmail.com: -- nosy: +fwierzbicki ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24450 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24460] urlencode() of dictionary not as expected
New submission from David Rueter:
In Python 3.4 I would like to serialize a dictionary into a URL-encoded string.
Given a dictionary like this:
thisDict = {'SomeVar1': [b'abc'], 'SomeVar2': [b'def'], 'SomeVar3':
[b'ghi']}
I would like to be able to return this string:
SomeVar1=abcSomeVar2=defSomeVar3=ghi
I thought that urllib.parse.urlencode would work for me, but it does not:
print(urllib.parse.urlencode(thisDict))
SomeVar1=%5Bb%27abc%27%5DSomeVar2=%5Bb%27def%27%5DSomeVar3=%5Bb%27ghi%27%5D
In other words, urlencode on the dictionary is performing a URL encode on the
string that is returned when the dictionary is cast to a string...and is
including the square brackets (escaped) and the byte literal b indicator.
{'SomeVar1': [b'abc'], 'SomeVar2': [b'def'], 'SomeVar3': [b'ghi']}
I can obtain the desired string with this:
''.join({!s}={!s}.format(key,urllib.parse.quote_plus(str(val[0],'utf-8')))
for (key,val) in thisDict.items())
Is the behavior of urllib.parse.urlencode() on a dictionary intentional? When
would the current behavior ever be useful?
Would it make sense to change the behavior of urllib.parse.urlencode such that
it works as described above?
--
components: Library (Lib)
messages: 245431
nosy: drue...@assyst.com
priority: normal
severity: normal
status: open
title: urlencode() of dictionary not as expected
type: behavior
versions: Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24460
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24461] os.environ.get treats Environt variant with double quotation marks wrong
进陆 added the comment:
the patched method should be
[quote]
if os.name=='nt' and res:
res=res.replace('', '')
[/quote]
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24461
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24460] urlencode() of dictionary not as expected
Gareth Rees added the comment: If you read the documentation for urllib.parse.urlencode [1], you'll see that it says: The value element in itself can be a sequence and in that case, if the optional parameter doseq is evaluates to True, individual key=value pairs separated by '' are generated for each element of the value sequence for the key. So you need to write: urllib.parse.urlencode(thisDict, doseq=True) 'SomeVar3=ghiSomeVar1=abcSomeVar2=def' [1]: https://docs.python.org/3/library/urllib.parse.html#urllib.parse.urlencode -- nosy: +Gareth.Rees ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24460 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20362] longMessage attribute is ignored in unittest.TestCase.assertRegexpMatches etc
Changes by Torsten Bronger bron...@physik.rwth-aachen.de: -- nosy: +bronger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20362 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24461] os.environ.get treats Environt variant with double quotation marks wrong
New submission from 进陆:
On windows, if a Directory/Filename has SPACE, double quotation mark should be
used. For example, R:\just a test\hello.bat has only one line @echo hello
world, so in the dos prompt
[quote]
R:\just a testhello.bat
hello world
R:\just a testcd ..
R:\set dir1=R:\just a test
R:\set dir2=R:\just a test
R:\%dir1%\hello.bat
hello world
R:\%dir2%\hello.bat
'R:\just' is not recognized as an internal or external command
[/quote]
Then, in python (it seems to be a common problem in all(?) python version)
[quote]
dir1= os.environ.get('dir1')
print (dir1)
print (os.path.isdir(dir1))
print (os.path.isdir(dir1.replace('', '')))
print ('*'*10)
dir2= os.environ.get('dir2')
print (dir2)
print (os.path.isdir(dir2))
print (os.path.isdir(dir2.replace('', '')))
[/quote]
displays
[quote]
R:\just a test
False --obviously, the double quotation marks is treated as
the part of the directory name by python, so the answer is wrong
True
**
R:\just a test
True
True
[/quote]
the patched method is simple
[quote]
if os.name=='nt':
res=res.replace('', '')
[/quote]
but the not simple thing is that os.py for python 3.4.3 changes a lot than
os.py for python 2.7, I get lost while reading os.py for python 3.4.3 by no
IDE. So I just report this issue, sorry.
--
components: Library (Lib)
messages: 245433
nosy: 进陆
priority: normal
severity: normal
status: open
title: os.environ.get treats Environt variant with double quotation marks wrong
type: behavior
versions: Python 2.7, Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24461
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23883] __all__ lists are incomplete
Changes by Mauro S. M. Rodrigues maurosmrodrig...@gmail.com: Removed file: http://bugs.python.org/file39140/issue23883_fileinput.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23883 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23883] __all__ lists are incomplete
Changes by Mauro S. M. Rodrigues maurosmrodrig...@gmail.com: Added file: http://bugs.python.org/file39718/issue23883_fileinput.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23883 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24462] bytearray.find Buffer Over-read
New submission from JohnLeitch: The bytearray.find method suffers from a buffer over-read that can be triggered by passing a string equal in length to the buffer. The result is a read off the end of the buffer, which could potentially be exploited to disclose the contents of adjacent memory. Repro: var_kcjtxvgr = bytearray([0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44,0x41,0x42,0x43,0x44]) var_kcjtxvgr.find(\x41 * 0x58) Exception: 0:000 r eax=0002 ebx=0058 ecx=071adf41 edx= esi=071f2264 edi=0057 eip=1e081cf9 esp=0027fc2c ebp=071ae000 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206 python27!stringlib_find+0x169: 1e081cf9 0fbe0c2amovsx ecx,byte ptr [edx+ebp] ds:002b:071ae000=?? 0:000 dV str = 0x071adfa8 ABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCDABCD str_len = 0n2 sub = 0x071f2264 sub_len = 0n88 offset = 0n0 0:000 db ebp-0x10 071adff0 41 42 43 44 41 42 43 44-41 42 43 44 41 42 43 44 ABCDABCDABCDABCD 071ae000 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? 071ae010 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? 071ae020 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? 071ae030 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? 071ae040 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? 071ae050 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? 071ae060 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? 0:000 !analyze -v -nodb *** * * *Exception Analysis * * * *** FAULTING_IP: python27!stringlib_find+169 [c:\build27\cpython\objects\stringlib\find.h @ 22] 1e081cf9 0fbe0c2amovsx ecx,byte ptr [edx+ebp] EXCEPTION_RECORD: -- (.exr 0x) ExceptionAddress: 1e081cf9 (python27!stringlib_find+0x0169) ExceptionCode: c005 (Access violation) ExceptionFlags: NumberParameters: 2 Parameter[0]: Parameter[1]: 071ae000 Attempt to read from address 071ae000 CONTEXT: -- (.cxr 0x0;r) eax=0002 ebx=0058 ecx=071adf41 edx= esi=071f2264 edi=0057 eip=1e081cf9 esp=0027fc2c ebp=071ae000 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206 python27!stringlib_find+0x169: 1e081cf9 0fbe0c2amovsx ecx,byte ptr [edx+ebp] ds:002b:071ae000=?? FAULTING_THREAD: 1e90 DEFAULT_BUCKET_ID: INVALID_POINTER_READ PROCESS_NAME: pythonw.exe ERROR_CODE: (NTSTATUS) 0xc005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: EXCEPTION_PARAMETER2: 071ae000 READ_ADDRESS: 071ae000 FOLLOWUP_IP: python27!stringlib_find+169 [c:\build27\cpython\objects\stringlib\find.h @ 22] 1e081cf9 0fbe0c2amovsx ecx,byte ptr [edx+ebp] NTGLOBALFLAG: 200 APPLICATION_VERIFIER_FLAGS: 0 APP: pythonw.exe ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ LAST_CONTROL_TRANSFER: from 1e081ee5 to 1e081cf9 STACK_TEXT: 0027fc48 1e081ee5 071adfa8 071f2264 0058 python27!stringlib_find+0x169 0027fc5c 1e083ac1 071adfa8 071f2264 0058 python27!stringlib_find_slice+0x35 0027fcb4 1e083b20 0001 1e083b10 1e0aafd7 python27!bytearray_find_internal+0x81 0027fcc0 1e0aafd7 070880c8 071d7a10 07086170 python27!bytearray_find+0x10 0027fcd8 1e0edd10 07086170 071d7a10 python27!PyCFunction_Call+0x47 0027fd04 1e0f017a 0027fd5c 06cc7c80 06cc7c80 python27!call_function+0x2b0 0027fd74 1e0f1150 07060d60 06cc7c80 python27!PyEval_EvalFrameEx+0x239a 0027fda8 1e0f11b2 06cc7c80 07060d60 06ccba50 python27!PyEval_EvalCodeEx+0x690 0027fdd4 1e11707a 06cc7c80 06ccba50 06ccba50 python27!PyEval_EvalCode+0x22 0027fdec 1e1181c5 0710ee20
[issue24461] os.environ.get treats Environt variant with double quotation marks wrong
R. David Murray added the comment: This is working in pretty much the only way it can work. Python is correctly retrieving the string from the environment (it includes the quotation marks). It is correctly passing that string to os.path: os.path takes the exact string that represents the filename. In windows it would be equally valid to do this: set dir3=just a test %dir3%\hello.bat Your simple fix would not address that case (and would break existing programs that rely on the current behavior). There is no way to handle all the possible variations here. The only thing that can be done is what python does do: return exactly the string stored in the environment variable, and expect exactly the filename as input to functions that expect filenames. In many contexts in Windows it works perfectly fine to have the filename without quotes around it stored in the environment variable and to use that: dir %dir1% works fine, for example. The Windows rules for quoting are non-obvious and not completely consistent, I'm afraid, and there's nothing python can do to paper over that fact. -- nosy: +r.david.murray resolution: - not a bug stage: - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24461 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24460] urlencode() of dictionary not as expected
David Rueter added the comment:
Ah hah! Indeed, urlencode() does work on dictionaries as expected when
doseq=True. Thank you for clarifying.
FWIW I had read the documentation and the referenced examples multiple times. I
would like to make a few documentation suggestions for clarity.
1 ) Update
https://docs.python.org/3/library/urllib.parse.html#urllib.parse.urlencode
Where documentation currently says: When a sequence of two-element tuples is
used as the query argument, the first element of each tuple is a key and the
second is a value. The value element in itself can be a sequence and in that
case, if the optional parameter doseq is evaluates to True, individual
key=value pairs separated by '' are generated for each element of the value
sequence for the key. The order of parameters in the encoded string will match
the order of parameter tuples in the sequence.
Perhaps instead the following would be more clear: The query argument may be
a sequence of two-element tuples where the first element of each tuple is a key
and the second is a value. However the optional parameter doseq must then be
set to True in order to reliably generate individual key=value pairs separated
by '' for each element of the value sequence for the key, and to preserve the
sequence of the elements in the query parameter.
2) Update https://docs.python.org/3/library/urllib.request.html#urllib-examples
The examples are referenced from the documentation: Refer to urllib examples
to find out how urlencode method can be used for generating query string for a
URL or data for POST. However the example page provides contradictory
information and examples for this specific use case.
Currently the examples page says: The urllib.parse.urlencode() function takes
a mapping or sequence of 2-tuples and returns a string in this format. It
should be encoded to bytes before being used as the data parameter. The charset
parameter in Content-Type header may be used to specify the encoding. If
charset parameter is not sent with the Content-Type header, the server
following the HTTP 1.1 recommendation may assume that the data is encoded in
ISO-8859-1 encoding. It is advisable to use charset parameter with encoding
used in Content-Type header with the Request.
Perhaps instead the following would be more clear: The
urllib.parse.urlencode() query parameter can accept a mapping or sequence of
2-tuples and return a string in this format if the optional parameter doseq is
set to True. It should be encoded to bytes before being used as the query
parameter. The charset parameter in Content-Type header may be used to specify
the encoding. If charset parameter is not sent with the Content-Type header,
the server following the HTTP 1.1 recommendation may assume that the data is
encoded in ISO-8859-1 encoding. It is advisable to use charset parameter with
encoding used in Content-Type header with the Request.
3) Also on the example page, there are examples of urlencode operating on
dictionaries where doseq is not provided. This is confusing. It would be
better to show doseq = True:
Here is an example session that uses the GET method to retrieve a URL
containing parameters:
...
data = urllib.parse.urlencode({'spam': 1, 'eggs': 2, 'bacon': 0})
...
The following example uses the POST method instead. Note that params output
from urlencode is encoded to bytes before it is sent to urlopen as data:
...
data = urllib.parse.urlencode({'spam': 1, 'eggs': 2, 'bacon': 0})
I suggest that these examples read:
data = urllib.parse.urlencode({'spam': 1, 'eggs': 2, 'bacon': 0},
doseq=true)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24460
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24460] urlencode() of dictionary not as expected
R. David Murray added the comment: That behavior is complex enough that I think it would be worth adding an example of it to the examples section (and maybe linking directly from the doseq explanation to that specific example). -- assignee: - docs@python components: +Documentation nosy: +docs@python, r.david.murray versions: +Python 3.5, Python 3.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24460 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24400] Awaitable ABC incompatible with functools.singledispatch
Yury Selivanov added the comment: Nick, Stefan, Martin, Please find an updated patch attached. All issues that you guys found (thanks a lot for the reviews btw!) should be resolved. -- Added file: http://bugs.python.org/file39720/corotype.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24400 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24450] Add gi_yieldfrom calculated property to generator object
Yury Selivanov added the comment: I think we need some feedback from PyPy Jython guys on this. I'm not sure that they can expose 'yieldfrom' slot without some performance penalties. -- nosy: +yselivanov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24450 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24439] Feedback for awaitable coroutine documentation
Yury Selivanov added the comment: Martin, thanks a lot for the feedback and patch! I'll review the patch when issue24400 lands. -- assignee: docs@python - yselivanov nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24439 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23996] _PyGen_FetchStopIterationValue() crashes on unnormalised exceptions
Changes by Yury Selivanov yseliva...@gmail.com: -- nosy: +yselivanov resolution: fixed - stage: resolved - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23996 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7518] Some functions in pymath.c should be moved elsewhere.
Mark Dickinson added the comment: Yes, there are almost certainly better ways to organize the build here. A hacky solution might be to simply #include _math.c in the two other files that need it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7518 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24450] Add gi_yieldfrom calculated property to generator object
Changes by Yury Selivanov yseliva...@gmail.com: -- assignee: - yselivanov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24450 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24380] Got warning when compiling _scproxy.c on Mac
Ronald Oussoren added the comment:
The patch is not correct.
You're probably building with a new enough version of OSX as the deployment
target. _scproxy.c should recognise this and should only perform the != NULL
test when the variable address might be NULL.
#if MAC_OS_X_VERSION_MIN_REQUIRED MAC_OS_X_VERSION_10_4
if (if (kSCPropNetProxiesExcludeSimpleHostnames != NULL) {
#end
#if MAC_OS_X_VERSION_MIN_REQUIRED = MAC_OS_X_VERSION_10_4
} else {
...
}
#endif
And as the variable is available on OSX 10.4 we could just drop the test and
assume it is available.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24380
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24462] bytearray.find Buffer Over-read
Changes by Serhiy Storchaka storch...@gmail.com: -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24462 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
