[issue28838] Uniformize argument names of "call" functions (C API)

STINNER Victor added the comment: I pushed a change which is rename.patch with fixes on comments in abstract.h. It seems like comments were no more revelant or moved to random places. I moved many comments, rewrote some of them, etc. Some comments were wrong like "This is the equivalent of

[issue28879] smtplib send_message should add Date header if it is missing, per RFC5322

R. David Murray added the comment: As I implied but did not say explicitly, this is the expected behavior of smtplib. You are responsible for adding any headers to the message that you want smtplib to send. In particular, the 'sendmail' method takes a string to send, and smtplib does not

[issue28879] smtplib RFC 5322 date header missing

Henning von Bargen added the comment: I can give a little more information. First, I created a very simple stand-alone test script (for Python >= 2.6): #!/bin/env python # -*- coding: utf-8 -*- import smtplib # Adjust these! HOST = "smtp.nowhere.local" PORT = 25 from_name = u"Test Python

[issue28838] Using consistent naming for arguments of "call" functions (C API)

R. David Murray added the comment: "Uniformize" isn't really an English word :) -- nosy: +r.david.murray title: Uniformize argument names of "call" functions (C API) -> Using consistent naming for arguments of "call" functions (C API) ___ Python

[issue28887] Login with Google not working on PyPi site

New submission from WayEasy Corporation: When I try to login with Google I don't get an error but I'm not logged in either. -- messages: 282550 nosy: WayEasy Corporation priority: normal severity: normal status: open title: Login with Google not working on PyPi site type: performance

[issue28838] Uniformize argument names of "call" functions (C API)

Roundup Robot added the comment: New changeset e6ad41a3f3bd by Victor Stinner in branch 'default': Uniformize argument names of "call" functions https://hg.python.org/cpython/rev/e6ad41a3f3bd -- nosy: +python-dev ___ Python tracker

[issue27030] Remove deprecated re features

Roundup Robot added the comment: New changeset 1b162d6e3d01 by Serhiy Storchaka in branch '3.6': Issue #27030: Unknown escapes in re.sub() replacement template are allowed https://hg.python.org/cpython/rev/1b162d6e3d01 New changeset 5904d2ced3d8 by Serhiy Storchaka in branch 'default': Merge

[issue28883] Python 3.5.2 crashers (from PyPy)

Brett Cannon added the comment: Victor for C4. -- nosy: +brett.cannon, haypo ___ Python tracker ___ ___

[issue27629] Cannot create ssl.SSLSocket without existing socket

nemunaire added the comment: The documentation already recommends to use SSLContext.wrap_socket(), but it didn't cover all use cases. Eg. I use multiple inheritance to handle both socket and SSLSocket inside a factory pattern, in order to override some methods defined in both classes. If I

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Yury Selivanov added the comment: I'll take a look at s1 later tonight -- ___ Python tracker ___ ___

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Brett Cannon added the comment: Victor & Yury for S1. -- nosy: +haypo, yselivanov ___ Python tracker ___ ___

[issue28888] Installer fails when newer version of CRT is pending installation

New submission from Steve Dower: We just discovered an issue where CPython install can fail on Windows 8, 8.1 and Server 2012. * do not install the recommended UCRT update * install any other Windows Update that requires a reboot * install the *latest* VC Redist and do not reboot * install

[issue28838] Using consistent naming for arguments of "call" functions (C API)

STINNER Victor added the comment: I pushed another large patch to "fix" the indentation of abstract.h. I would prefer to also have this "reindent" change on review, but our reviewing tool doesn't support patch series :-( Attached cleanup.patch reformats deeply the header file to use the same

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

Brett Cannon added the comment: Serhiy's patch LGTM. -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue27629] Cannot create ssl.SSLSocket without existing socket

Changes by nemunaire : Removed file: http://bugs.python.org/file43927/fix_sslsocket_init_without_socket_3_3-3_6.patch ___ Python tracker ___

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Gregory P. Smith added the comment: +larry for (S2) regarding argument clinic's treatment of bool. -- nosy: +gregory.p.smith, larry ___ Python tracker

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Gregory P. Smith added the comment: attaching a proposed fix for (S5). os.chmod should have the same EINTR retry treatment as everything else. That it does not appears to have been an oversight. -- keywords: +patch Added file:

[issue28891] Standardise more behaviours for zero-argument super() __class__ and __classcell__

New submission from Nick Coghlan: In http://bugs.python.org/issue28884#msg282535 Armin Rigo points out that the zero-argument super() cell injection currently interacts a little strangely with explicit "nonlocal __class__" statements in nested namespaces. Specifically, it acts like a closure

[issue28091] Document PEP 525

Yury Selivanov added the comment: Friday is good, take your time! -- ___ Python tracker ___ ___

[issue28867] NamedTemporaryFile does not generate a ResourceWarning for unclosed files (unlike TemporaryFile)

Changes by Jon Dufresne : -- keywords: +patch Added file: http://bugs.python.org/file45783/namedtemporaryfile-resourcewarning.patch ___ Python tracker

[issue28886] Move deprecated abc module decorators to separate section in docs

Changes by Serhiy Storchaka : -- nosy: -serhiy.storchaka ___ Python tracker ___

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

Serhiy Storchaka added the comment: Should the original exception be stored on the __context__ or the __cause__ attribute? In the latter case you should use _PyErr_FormatFromCause(). -- ___ Python tracker

[issue28867] NamedTemporaryFile does not generate a ResourceWarning for unclosed files (unlike TemporaryFile)

SilentGhost added the comment: The ResourceWarning that you've introduced need to be "fixed" in a few place in test_urllib2 -- stage: -> needs patch versions: +Python 3.7 ___ Python tracker

[issue28866] Type cache is not correctly invalidated on a class defining mro()

Julien Palard added the comment: > issue28866.diff always invalidates the cache, so it works. But it is > suboptimal, IMO it defeats the whole purpose of a cache. Not sure about defeating the purpose of the cache as I only invalidate in setattr, getattr are still cache hitting. I tried: $

[issue28887] Login with Google not working on PyPi site

SilentGhost added the comment: This is the wrong bug tracker. The issue seems to have already been reported to pypa https://github.com/pypa/pypi-legacy/issues/492 -- nosy: +SilentGhost resolution: -> not a bug stage: -> resolved status: open -> closed type: performance -> behavior

[issue28882] RFC: Slice confusing with negative strides and the 0th element.

Josh Rosenberg added the comment: I find this report nigh incomprehensible, but I will admit that I can't seem to find any good explanations of the extended slicing rules in the Python docs. The tutorial covers slicing, but, AFAICT, it never mentions extended slicing at all, not in 3.1.2 or

[issue28892] pandas.to_datetime crashes in 3.6b4

New submission from Dale: I'm trying 3.6b4 on my mac (OS X 10.10.5) and when I run the following code (after doing pip install numpy and pandas) I see a 'SystemError': >>> import pandas as pd >>> pd.to_datetime('10/31/2016') ValueError: Error parsing datetime string "10/31/2016" at position 2

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

New submission from Yury Selivanov: Originally reported in http://bugs.python.org/issue28885#msg282538 Ned, please take a look at the attached patch. While I think that the change is quite small & safe to merge, I think it's OK if we push this only in 3.6.1. It's a nice usability

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Yury Selivanov added the comment: I created an issue to track S1: http://bugs.python.org/issue28893 -- ___ Python tracker ___

[issue28892] pandas.to_datetime crashes in 3.6b4

Dale added the comment: Thanks for the quick response! -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue28091] Document PEP 525

Yury Selivanov added the comment: Eric, are you working on a patch? If not, I'll be focusing on this myself in the next couple of days. -- ___ Python tracker

[issue28886] Move deprecated abc module decorators to separate section in docs

Nick Coghlan added the comment: Right, these are in the "Don't use them in new code, but we have absolutely no plans to actually remove them" documentation-only category of deprecation warning. However, I'm converting this to a documentation enhancement request, as the documentation could

[issue24254] Make class definition namespace ordered by default

Nick Coghlan added the comment: Thanks for the ping Ned. Closing this again, as Guido explained the rationale for the change in the python-dev thread referenced above: https://mail.python.org/pipermail/python-dev/2016-September/146371.html -- resolution: -> fixed stage: commit

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Nick Coghlan added the comment: I broke B9 for the "nonlocal __class__" misbehaviour out to a separate issue: http://bugs.python.org/issue28891 I love zero-argument super() as a user, but as an interpreter maintainer... ugh :P -- nosy: +ncoghlan

[issue28091] Document PEP 525

Eric Appelt added the comment: Hi Yury - Yes, I am excited about doing this and getting to work on it. Today was pretty busy but I have some time blocked out tomorrow to really dig in. I was planning to give myself a deadline of Friday afternoon if that works for the review/release schedule.

[issue28838] Using consistent naming for arguments of "call" functions (C API)

Serhiy Storchaka added the comment: Oh, you have mixed up comments! In headers descriptions are written after function declarations. You have moved some comments and now some descriptions are placed below the corresponding declaration, and some descriptions are placed above. Now it is not

[issue27030] Remove deprecated re features

Ned Deily added the comment: It is unfortunate that the deprecation note did not explicitly mention replacement templates as well as regexp patterns. While there are good arguments to be made for either case, I think it makes more sense to treat the replacement template as following the

[issue28879] smtplib send_message should add Date header if it is missing, per RFC5322

Eric Lafontaine added the comment: Hi, Not sure this is where the comment goes... I work with the smtplib and email libraries. I understand Henning von Bargen when he say that we should have a way to support RFC 5322 without asking the user to understand how to support it. The issue is

[issue28838] Using consistent naming for arguments of "call" functions (C API)

Roundup Robot added the comment: New changeset 69c7451c3ec1 by Victor Stinner in branch 'default': Issue #28838: Fix weird indentation of abstract.h https://hg.python.org/cpython/rev/69c7451c3ec1 -- ___ Python tracker

[issue28891] Standardise more behaviours for zero-argument super() __class__ and __classcell__

Nick Coghlan added the comment: Breaking the concrete proposal out to its own post: - for CPython, "nonlocal __class__" becomes a SyntaxError generated by the symbol table pass in the compiler in 3.7+ and a DeprecationWarning in 3.6.1+ - other implementations (including PyPy) can just make

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Larry Hastings added the comment: I assert that Argument Clinic's / PyArg_ParseTuple's handling of bool is correct. * Python has a well-established concept of "truth": https://docs.python.org/3/library/stdtypes.html#truth-value-testing The C equivalent is, indeed, PyObject_IsTrue(). *

[issue28892] pandas.to_datetime crashes in 3.6b4

Ned Deily added the comment: Thanks for the report. This problem was reported previously in Issue28636 where it was determined that the problem is in Pandas (https://github.com/pandas-dev/pandas/issues/14561). It looks like the Pandas project has pushed a fix for it. -- resolution:

[issue28838] Using consistent naming for arguments of "call" functions (C API)

Serhiy Storchaka added the comment: > It don't think that my change makes abstract.h worse, some comments were far > from their declaration, and there is was no unique style for comments. It's > a mess. Seems most of comments that did not follow common style are your comments to "fast call"

[issue28889] IDLE needs the ability to pass in command-line arguments

New submission from Raymond Hettinger: [--- Feature request posted on behalf of Balakrishnan Sakthidharan ---] IDLE lets you run scripts with F5. What is needs is an F6 that opens a dialog box and asks for command-line arguments. This will help develop and test command line scripts in the

[issue28886] Deprecated abstract base class (abc) decorators do not raise DeprecationWarning

Serhiy Storchaka added the comment: Not all features deprecated in the source should be deprecated in the code. May be reasons for not doing this in the code. Adding the deprecation in maintained releases can introduce a regression. It seems to me that these decorators are not broken. They is

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

Roundup Robot added the comment: New changeset aaee06743c61 by Ned Deily in branch '3.6': Issue #28835: Tidy previous showwarning changes based on review comments. https://hg.python.org/cpython/rev/aaee06743c61 New changeset 7bca3bf6401a by Ned Deily in branch 'default': Issue #28835: merge

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

Ned Deily added the comment: Thanks everyone for getting this resolved for 360rc1! -- priority: release blocker -> resolution: -> fixed stage: commit review -> resolved status: open -> closed versions: +Python 3.7 ___ Python tracker

[issue27030] Remove deprecated re features

Ned Deily added the comment: Thanks, Serhiy, for reverting the error handling for 3.6.0 (in 3.6.0rc1). I'm going to mark this as closed. Issue28450 is still open at the moment regarding the documentation and possible 3.7 changes. -- priority: release blocker -> resolution: ->

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Ned Deily added the comment: Note that 1b162d6e3d01 in Issue27030 (for 3.6.0rc1) has changed the behavior for re.sub replacement templates to produce a deprecation warning in 3.6 while still being treated as an error in 3.7. -- ___ Python tracker

[issue28742] argparse.ArgumentDefaultsHelpFormatter sometimes provides inaccurate documentation of defaults, so they should be overrideable

Peter Eckersley added the comment: OK, here's another solution following paul.j3's suggestion. I think this is much better: https://gist.github.com/pde/817a00378d3f6ed73747dfffce323ae5 Tests & documentation included. -- ___ Python tracker

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

Serhiy Storchaka added the comment: I don't understand why test_showwarnmsg_missing was added. Why deleting warnings._showwarnmsg should be supported? I would rename _showwarning to _showwarning_orig for accenting it's purpose. It is used only for checking if showwarning was replaced by the

[issue28089] asyncio: Document that TCP_NODELAY is now used by default

Roundup Robot added the comment: New changeset 150d36dbe3ba by Victor Stinner in branch '3.6': warnings: Fix the issue number https://hg.python.org/cpython/rev/150d36dbe3ba -- ___ Python tracker

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

Roundup Robot added the comment: New changeset 150d36dbe3ba by Victor Stinner in branch '3.6': warnings: Fix the issue number https://hg.python.org/cpython/rev/150d36dbe3ba -- nosy: +python-dev ___ Python tracker

[issue28724] Add method send_io, recv_io to the socket module.

Christian Heimes added the comment: Take your time, feature freeze for 3.7 is in about 18 months from now. -- ___ Python tracker ___

[issue27971] utf-16 decoding can't handle lone surrogates

Changes by Christoph Reiter : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___

[issue28089] asyncio: Document that TCP_NODELAY is now used by default

Roundup Robot added the comment: New changeset 726308cfe3b5 by Victor Stinner in branch '3.6': catch_warnings() calls showwarning() if overriden https://hg.python.org/cpython/rev/726308cfe3b5 -- nosy: +python-dev ___ Python tracker

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

STINNER Victor added the comment: I pushed a more complete version of my patch: New changeset 726308cfe3b5 by Victor Stinner in branch '3.6': catch_warnings() calls showwarning() if overriden https://hg.python.org/cpython/rev/726308cfe3b5 I dislike pushing a different change than the reviewed

[issue27030] Remove deprecated re features

Serhiy Storchaka added the comment: Here is a patch that partially reverts changes of issue27030. It allows using unknown escapes in re.sub() replacement template, but they are deprecated and will be errors in 3.7. If this is good to you Barry, and Ned allows, it can be committed in 3.6 only.

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

STINNER Victor added the comment: Julien reviewed the pushed change and asked me questions on IRC: * "nonlocal log": this change is unrelated to the fix, I should have done that in a separated change, sorry, I cannot resist to refactoring :-) The change has no effect, it's more cosmetic to

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

Serhiy Storchaka added the comment: Here is a patch that cleans up the code. -- Added file: http://bugs.python.org/file45775/showwarning-tidy.patch ___ Python tracker

[issue28838] Uniformize argument names of "call" functions (C API)

STINNER Victor added the comment: rename.patch: Big patch to rename function parameters. -- Added file: http://bugs.python.org/file45776/rename.patch ___ Python tracker

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Serhiy Storchaka added the comment: (S4) was fixed in 3.6 (issue18018). But the fix was not applied to 3.5. -- dependencies: +SystemError: Parent module '' not loaded, cannot perform relative import nosy: +brett.cannon, serhiy.storchaka ___ Python

[issue28883] Python 3.5.2 crashers (from PyPy)

Armin Rigo added the comment: (C6) I didn't try, but it seems that typeobject.c:mro_internal() is prone to a refcount crash. It does this:: old_mro = type->tp_mro; ...mro_invoke()... /* might cause reentrance */ type->tp_mro = new_mro; ... Py_XDECREF(old_mro);

[issue28883] Python 3.5.2 crashers (from PyPy)

New submission from Armin Rigo: As discussed on python-dev, I am creating omnibus issues from the lists of crashers, of wrong-according-to-the-docs, and of strange-behavior-only issues that I found while developing Python 3.5.2 support for PyPy. These occur with CPython 3.5.2 but most of

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Changes by Armin Rigo : -- type: -> behavior ___ Python tracker ___ ___

[issue28883] Python 3.5.2 crashers (from PyPy)

Changes by Armin Rigo : -- type: -> crash ___ Python tracker ___ ___

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Armin Rigo added the comment: (B1) on modern Linux: if the first call in the process to socketpair() ends in a EINVAL, then cpython will (possibly wrongly) assume it was caused by SOCK_CLOEXEC and not use SOCK_CLOEXEC at all in the future --

[issue28883] Python 3.5.2 crashers (from PyPy)

Armin Rigo added the comment: (C4) faulthandler: register(): the signal handler, faulthandler_user(), changes errno in faulthandler_dump_traceback() but fails to restore it if chain=False. This can rarely cause random nonsense in the main program. --

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Armin Rigo added the comment: (B3) re.sub(b'y', bytearray(b'a'), bytearray(b'xyz')) -> b'xaz' re.sub(b'y', bytearray(b'\\n'), bytearray(b'xyz')) -> internal TypeError -- ___ Python tracker

[issue28883] Python 3.5.2 crashers (from PyPy)

Changes by Armin Rigo : -- Removed message: http://bugs.python.org/msg282524 ___ Python tracker ___

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Armin Rigo added the comment: (B2) fcntl.ioctl(x, y, buf, mutate_flag): mutate_flag is there for the case of buf being a read-write buffer, which is then mutated in-place. But if we call with a read-only buffer, mutate_flag is ignored (instead of rejecting a True value)---ioctl(x, y,

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Armin Rigo added the comment: (B4) if you have a stack of generators where each is in 'yield from' from the next one, and you call '.next()' on the outermost, then it enters and leaves all intermediate frames. This is costly but may be required to get the sys.settrace()/setprofile() hooks

[issue28883] Python 3.5.2 crashers (from PyPy)

Armin Rigo added the comment: (C6) I didn't try, but it seems that typeobject.c:mro_internal() is prone to a refcount crash. It does this:: old_mro = type->tp_mro; ...mro_invoke()... /* might cause reentrance */ type->tp_mro = new_mro; ... Py_XDECREF(old_mro);

[issue28883] Python 3.5.2 crashers (from PyPy)

Armin Rigo added the comment: (C5) setting f_lineno didn't evolve when the rest of the bytecodes evolved, which means it is not safe any more:: import sys def f(): try: raise ValueError# line 5 except ValueError: print(42) # line

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

New submission from Armin Rigo: As discussed on python-dev, I am creating omnibus issues from the lists of crashers, of wrong-according-to-the-docs, and of strange-behavior-only issues that I found while developing Python 3.5.2 support for PyPy. These occur with CPython 3.5.2 but most of

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Armin Rigo added the comment: (S4) if you write ``from .a import b`` inside the Python prompt, or in a module not in any package, then you get a SystemError(!) with an error message that is unlikely to help newcomers. -- ___ Python tracker

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

New submission from Armin Rigo: As discussed on python-dev, I am creating omnibus issues from the lists of crashers, of wrong-according-to-the-docs, and of strange-behavior-only issues that I found while developing Python 3.5.2 support for PyPy. These occur with CPython 3.5.2 but most of

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Serhiy Storchaka added the comment: About (B10) see issue18961 and issue25937. -- dependencies: +DIfference between utf8 and utf-8 when i define python source code encoding., Non-UTF8 encoding line nosy: +serhiy.storchaka ___ Python tracker

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Serhiy Storchaka added the comment: (S2) is related not to Argument Clinic itself, but to the 'p' format unit added in 3.3 (issue14705). -- ___ Python tracker

[issue28886] Deprecated abstract base class (abc) decorators do not raise DeprecationWarning

New submission from John Hagen: In the abc module (https://docs.python.org/3/library/abc.html) the following decorators have been deprecated since Python 3.3: - abstractclassmethod - abstractstaticmethod - abstractproperty But if you run the following example code using Python 3.5.2 with

[issue28883] Python 3.5.2 crashers (from PyPy)

Armin Rigo added the comment: os.scandir() returns an iterable object that should not be used from multiple threads. Doing so can e.g. cause one thread to close the dirp while another thread is still using it. This is likely to crash. Similarly, the test for (!iterator->dirp) at the

[issue28883] Python 3.5.2 crashers (from PyPy)

Armin Rigo added the comment: (C2) os.scandir() direntry objects should not have stat() called from two threads concurrently. It will make two stat objects and leak one of them. -- ___ Python tracker

[issue28883] Python 3.5.2 crashers (from PyPy)

Armin Rigo added the comment: (C3) _PyGen_yf() checks the opcode at [f_lasti + 1], which is the next opcode that will run when we resume the generator: either it is the opcode following the YIELD, or it is exactly YIELD_FROM. It is not possible at the moment to write Python code that

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Armin Rigo added the comment: (B10) Follow-up on issue #25388: running ``python x.py`` if x.py contains the following bytes... * ``b"#\xfd\n"`` => we get a SyntaxError: Non-UTF-8 code * ``b"# coding: utf-8\n#\xfd\n"`` => we get no error! --

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Armin Rigo added the comment: (B9) CPython 3.5.2: this ``nonlocal`` seems not to have a reasonable effect (note that if we use a different name instead of ``__class__``, this example correctly complain that there is no binding in the outer scope of ``Y``):: class Y: class X:

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Changes by Armin Rigo : -- versions: +Python 3.5 ___ Python tracker ___ ___

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Armin Rigo added the comment: (B5) this is an old issue that was forgotten twice on the issue tracker: ``class C: __new__=int.__new__`` and ``class C(int): __new__=object.__new__`` can each be instantiated, even though they shouldn't. This is because ``__new__`` is completely ignored if

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Armin Rigo added the comment: (B6) this program fails the check for no sys.exc_info(), even though at the point this assert runs (called from the <== line) we are not in any except/finally block. This is a generalization of test_exceptions:test_generator_doesnt_retain_old_exc::

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Armin Rigo added the comment: (S2) argument clinic turns the "bool" specifier into PyObject_IsTrue(), accepting any argument whatsoever. This can easily get very confusing for the user, e.g. after messing up the number of arguments. For example: os.symlink("/path1", "/path2", "/path3")

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Armin Rigo added the comment: (S5) pep 475: unclear why 'os.fchmod(fd)' retries automatically when it gets EINTR but the otherwise-equivalent 'os.chmod(fd)' does not. (The documentation says they are fully equivalent, so someone is wrong.) --

[issue28838] Uniformize argument names of "call" functions (C API)

Serhiy Storchaka added the comment: Added comments on Rietveld. I think we can keep "func" instead of "callable" in the source code for decreasing the number of changes. -- ___ Python tracker

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Armin Rigo added the comment: (S3) hash({}.values()) works (but hash({}.keys()) correctly gives TypeError). That's a bit confusing and, as far as I can tell, always pointless. Also, related: d.keys()==d.keys() but d.values()!=d.values(). --

[issue28885] Python 3.5.2 strange-behavior issues (from PyPy)

Armin Rigo added the comment: (S1) ceval.c: GET_AITER: calls _PyCoro_GetAwaitableIter(), which might get an exception from calling the user-defined __await__() or checking what it returns; such an exception is completely eaten. -- ___ Python

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Armin Rigo added the comment: (B7) frame.clear() does not clear f_locals, unlike what a test says (Lib/test/test_frame.py):: def test_locals_clear_locals(self): # Test f_locals before and after clear() (to exercise caching) f, outer, inner = self.make_frames()

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Armin Rigo added the comment: (B8) also discussed in connection with https://bugs.python.org/issue28427 weak dicts (both kinds) and weak sets have an implementation of __len__ which doesn't give the "expected" result on PyPy, and in some cases on CPython too. I'm not sure what is

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Changes by Armin Rigo : -- type: -> behavior ___ Python tracker ___ ___

[issue28884] Python 3.5.2 non-segfaulting bugs (from PyPy)

Serhiy Storchaka added the comment: About (B3): Only str and bytes are supported. The support of bytearray templates is not documented and is not guarantied. -- ___ Python tracker

[issue28890] logging.handlers: Document that QueueListener is a daemon thread

Changes by Julien Castiaux : -- assignee: docs@python components: Documentation nosy: Julien Castiaux, docs@python priority: normal severity: normal status: open title: logging.handlers: Document that QueueListener is a daemon thread type: enhancement

[issue24254] Make class definition namespace ordered by default

Ned Deily added the comment: What's the status of this issue? It's still marked as a "deferred blocker" for 3.6. -- nosy: +ned.deily ___ Python tracker

[issue28339] "TypeError: Parameterized generics cannot be used with class or instance checks" in test_functools after importing typing module

Ned Deily added the comment: This is still marked as "deferred blocker". Is there anything more that needs to be done for 3.6.0? I'm assuming not. -- ___ Python tracker

  1   2   >