[issue32288] Inconsistent behavior with slice assignment?

Massimiliano Culpo added the comment: Hi Serhiy, I briefly checked out Python 3.7.0b3, and saw no changes with respect to: - Documenting what is the exact meaning of "extended slice" (but that now is also tracked by issue 32289) - Improving the

[issue33453] from __future__ import annotations breaks dataclasses ClassVar and InitVar handling

Ned Deily added the comment: > Ned, this is after the last beta but as far as I understand, we're still > fine committing fixes that maintain ABI until RC1, right? Yes -- ___ Python tracker

[issue33453] from __future__ import annotations breaks dataclasses ClassVar and InitVar handling

Change by Łukasz Langa : -- Removed message: https://bugs.python.org/msg316344 ___ Python tracker ___

[issue33453] from __future__ import annotations breaks dataclasses ClassVar and InitVar handling

Łukasz Langa added the comment: Well, this is a rather big deal and I'd like to see it solved for 3.7.0. Ned, this is after the last beta but as far as I understand, we're still fine committing fixes that maintain ABI until RC1, right? Note that this isn't specific to the

[issue33453] from __future__ import annotations breaks dataclasses ClassVar and InitVar handling

Łukasz Langa added the comment: Well, this is a rather big deal and I'd like to see it solved for 3.7.0. Ned, this is after the last beta but as far as I understand, we're still Note that this isn't specific to the `annotations` future import. If a user actually writes:

[issue33452] add user notification that parent init will not be called in dataclass init method

Rick Teachey added the comment: The init method that comes up for int, str, float, etc is just the object init: assert int.__init__ is object.__init__ Probably the thing to do is grab any init methods that aren't the object.__init__ while stripping out the

[issue27675] IDLE file completion has 2 bugs depending on open quote used

Cheryl Sabella added the comment: Thanks, Terry! I'm able to recreate the autocomplete issue on Windows 7 using 3.6.3, but not on Ubuntu. As you said, the color issue seems fine now for both platforms. I'll take a look at those other issues for the test cases. --

[issue33452] add user notification that parent init will not be called in dataclass init method

Change by Eric V. Smith : -- assignee: -> eric.smith ___ Python tracker ___ ___

[issue16733] Solaris ctypes_test failures

Greg Onufer added the comment: Or probably just change the type of the bitfield from "int" to "signed int"! -- ___ Python tracker

[issue33452] add user notification that parent init will not be called in dataclass init method

Eric V. Smith added the comment: I'm okay with the concept, but I don't know how to implement it. You need to not only know if a class has a __init__, but also if it's expected to be called. For example, these don't normally get called, but if you inherit from them (and

[issue21983] segfault in ctypes.cast

miss-islington added the comment: New changeset 8ac158a6dfb86880e22003afe0ff39ec31b0a094 by Miss Islington (bot) in branch '3.6': bpo-21983: Fix a crash in ctypes.cast() when passed a ctypes structured data type (GH-3859)

[issue33453] from __future__ import annotations breaks dataclasses ClassVar and InitVar handling

Eric V. Smith added the comment: This is a known issue, but it wasn't being tracked here. So, thanks for opening the issue. https://github.com/ericvsmith/dataclasses/issues/92#issuecomment-382473127 Not to put Łukasz on the spot (he's sitting behind me even as we speak),

[issue21983] segfault in ctypes.cast

Steve Dower added the comment: The backport to 2.7 needs some help. I can't do it on my laptop for the next week, but I'll try to get to it eventually. Feel free to get there first. -- versions: +Python 3.6 ___ Python

[issue21983] segfault in ctypes.cast

Change by miss-islington : -- pull_requests: +6434 ___ Python tracker ___

[issue21983] segfault in ctypes.cast

Change by miss-islington : -- pull_requests: +6433 stage: backport needed -> patch review ___ Python tracker

[issue33453] from __future__ import annotations breaks dataclasses ClassVar handling

Rick Teachey added the comment: Sorry, mean to say it works just fine *without* the import. -- ___ Python tracker ___

[issue21983] segfault in ctypes.cast

Change by Steve Dower : -- assignee: -> steve.dower stage: patch review -> backport needed versions: +Python 3.8 -Python 3.4 ___ Python tracker

[issue33453] from __future__ import annotations breaks dataclasses ClassVar handling

Rick Teachey added the comment: To be clear: it works just fine with the annotations import. -- ___ Python tracker ___

[issue21983] segfault in ctypes.cast

Steve Dower added the comment: New changeset d518d8bc8d5dac1a1270612f424d33e0e5afc2b5 by Steve Dower (Oren Milman) in branch 'master': bpo-21983: Fix a crash in ctypes.cast() when passed a ctypes structured data type (GH-3859)

[issue33453] from __future__ import annotations breaks dataclasses ClassVar handling

New submission from Rick Teachey : This is broken in 3.7 (both beta 3 and 4): from __future__ import annotations from dataclasses import dataclass from typing import ClassVar, Any @dataclass class C(): class_var: ClassVar[Any] = object() data: str Traceback:

[issue33015] Fix function cast warning in thread_pthread.h

Steve Dower added the comment: Can't we just fix the cast? We shouldn't have to do heap allocations for this. -- nosy: +steve.dower ___ Python tracker

[issue33452] add user notification that parent init will not be called in dataclass init method

New submission from Rick Teachey : The dataclasses module is incredibly easy to use. This is a good thing. BUT one downside is it will definitely be utilized by people who don't have a thorough understanding of how it does what it does. Even for me, despite having a very

[issue33451] Start pyc file lock the file

New submission from Jean-Louis Tamburini : Python v3.6.4:d48eceb Windows 10.0.16299 I search on Internet and I don't find why Python Interpreter (v3.6.4) do that. With python 2.7, I don't have this "problem". When I launch script like : c:\Python364\python.exe

[issue33294] Support complex expressions for py-print command.

Martin Liška added the comment: May I please ping patch review.. -- ___ Python tracker ___

[issue33450] unexpected EPROTOTYPE returned by sendto on MAC OSX

New submission from Richard C : The following exception is raised unexpectedly on macOS versions 10.13, 10.12 & 10.11 at least. It appears to be macOS specific (works okay on Linux). Further information can be found at the following links:

[issue33449] Documentation for email.charset confusing about the location of constants

New submission from Francois Labelle : When mentioning the constants contained in the module email.charset, the documentation prefixes them with "Charset", for example: Charset.QP, Charset.BASE64, Charset.SHORTEST. This suggests that the constants can be found on the

[issue33448] Output_Typo_Error

Mark Dickinson added the comment: I can't reproduce. I'm looking at https://docs.python.org/3.6/tutorial/introduction.html#strings, and when I test things in Python 3.6.5, I see exactly the same output as given in the documentation: Python 3.6.5 (default, Mar 29 2018,

[issue33448] Output_Typo_Error

New submission from vishva patel : There is an out[ut typo error in the documentation of python in the module (An Informal Introductio To Python) 3.1.2 section Strings the first example last output the output of: >>>Isn\'t is given as Isn\t #but it shuld be >>>Isn\'t

[issue33419] Add functools.partialclass

Neil Girdhar added the comment: It seems like Python doesn't do very well with dynamically-generated classes. For that reason, I'm losing interest on this feature. Is there any interest in merging the documentation changes here:

[issue30167] site.main() does not work on Python 3.6 and superior if PYTHONSTARTUP is set

Change by steverweber : -- keywords: +patch pull_requests: +6432 stage: -> patch review ___ Python tracker ___

[issue16733] Solaris ctypes_test failures

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___

[issue33038] GzipFile doesn't always ignore None as filename

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue33414] Make shutil.copytree use os.scandir to take advantage of cached is_(dir|file|symlink)

Change by Serhiy Storchaka : -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue33038] GzipFile doesn't always ignore None as filename

Serhiy Storchaka added the comment: New changeset afe5f633e49e0e873d42088ae56819609c803ba0 by Serhiy Storchaka (Bo Bayles) in branch '2.7': bpo-33038: Fix gzip.GzipFile for file objects with a non-string name attribute. (GH-6095)

[issue32626] Subscript unpacking raises SyntaxError

Serhiy Storchaka added the comment: Issue32117 looks considering a more general question about iterable unpacking. -- nosy: +serhiy.storchaka resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Tuple unpacking in return and

[issue33311] cgitb: remove parentheses when the error is in module

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.8 ___ Python tracker

[issue33311] cgitb: remove parentheses when the error is in module

Serhiy Storchaka added the comment: New changeset 8cf4b34b3665b8bb39ea7111e6b5c3410899d3e4 by Serhiy Storchaka (sblondon) in branch 'master': bpo-33311: Do not display parameters displayed in parentheses for module call. (GH-6677)

[issue13525] Tutorial: Example of Source Code Encoding triggers error

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.6, Python 3.7, Python 3.8 -Python 3.2, Python 3.3 ___ Python tracker

[issue13525] Tutorial: Example of Source Code Encoding triggers error

Serhiy Storchaka added the comment: New changeset d7e783b17feaedbe0f5b30467cb7f43cefadf904 by Serhiy Storchaka in branch '2.7': [2.7] bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738). (GH-6744)

[issue32288] Inconsistent behavior with slice assignment?

Serhiy Storchaka added the comment: So this issue can be closed now? -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue32189] SyntaxError for yield expressions inside comprehensions & genexps

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue32055] Reconsider comparison chaining for containment tests

Serhiy Storchaka added the comment: On other hand, beginners are confused even by chained "==". There are regular reports about this on the tracker and questions on Python-related resources. I have found the chained "in" is useful in the following case

[issue13525] Tutorial: Example of Source Code Encoding triggers error

miss-islington added the comment: New changeset fa40fc0593012893e447875632e9ed3df277561f by Miss Islington (bot) in branch '3.6': bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738)

[issue13525] Tutorial: Example of Source Code Encoding triggers error

miss-islington added the comment: New changeset 834ea12ca6478d73a337ce52f33660f6f174 by Miss Islington (bot) in branch '3.7': bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738)

[issue6673] Uncaught comprehension SyntaxError eats up all memory

Serhiy Storchaka added the comment: "yield" in comprehensions is deprecated in 3.7: ../issue6673.py:22: DeprecationWarning: 'yield' inside list comprehension target.send([ (yield) for i in range(chunk_size) ]) and an error in 3.8: File "../issue6673.py", line

[issue13525] Tutorial: Example of Source Code Encoding triggers error

Change by Serhiy Storchaka : -- pull_requests: +6431 ___ Python tracker ___ ___

[issue13525] Tutorial: Example of Source Code Encoding triggers error

Change by miss-islington : -- pull_requests: +6430 ___ Python tracker ___

[issue13525] Tutorial: Example of Source Code Encoding triggers error

Change by miss-islington : -- pull_requests: +6429 ___ Python tracker ___

[issue13525] Tutorial: Example of Source Code Encoding triggers error

Serhiy Storchaka added the comment: New changeset ddb6215a55b0218b621d5cb755e9dfac8dab231a by Serhiy Storchaka in branch 'master': bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738)

[issue26701] Documentation for int constructor mentions __int__ but not __trunc__

Change by Serhiy Storchaka : -- pull_requests: +6428 ___ Python tracker ___ ___

[issue13525] Tutorial: Example of Source Code Encoding triggers error

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +6427 stage: needs patch -> patch review ___ Python tracker

[issue13525] Tutorial: Example of Source Code Encoding triggers error

Serhiy Storchaka added the comment: Error message was fixed. In all supported versions it is: $ ./python cp_1252broken.py File "cp_1252broken.py", line 1 SyntaxError: encoding problem: cp-1252 But the tutorial still contains non-working example. This is an easy

[issue27675] IDLE file completion has 2 bugs depending on open quote used

Terry J. Reedy added the comment: I believe the report in August 2016 was about the time of the preliminary.0a4 release, months before the final 3.6.0 release. Something could have easily changed after. I should have been more detailed and accurate is what I wrote. In

[issue27609] IDLE completions: format, factor, and fix

Terry J. Reedy added the comment: In re-verifying #27675, the color bug seems to be gone. The completion bug is still here, at least on Windows. It would be good to sort the issues by whether they appear to affect autocomplete.py or autocomplete_w.py or both. --