[issue28758] UnicodeDecodeError: 'gbk' codec can't decode byte 0xab in position 74: illegal multibyte sequence

Terry J. Reedy added the comment: So, does there appear to be a Python bug to fix or should this be closed? -- ___ Python tracker ___

[issue28288] Expose environment variable for Py_Py3kWarningFlag

Benjamin Peterson added the comment: Yes, I suppose this falls under the general exemption in 2.x for -3 warning changes. On Fri, Nov 25, 2016, at 09:13, Berker Peksag wrote: > > Berker Peksag added the comment: > > Roy's patch looks good to me in general. Benjamin, as the RM of 2.7, do > you

[issue28739] PEP 498: docstrings as f-strings

Guido van Rossum added the comment: I don't really care that much, but I personally think that it would be more consistent (and a simpler rule) if *no* f-string (not even ones without substitutions) were to be allowed as docstrings. In all other examples that Raymond shows it's the syntactic

[issue28739] PEP 498: docstrings as f-strings

Raymond Hettinger added the comment: [TJR] > I think this issue should either be closed as 'not a bug' > or redefined as a doc issue. I concur. FWIW, here are some comparisons. Not allowed: 'Not counted as' + ' a docstring' 'Not a docstring ' * 10 b'Also not a docstring'

[issue28804] file tell() report incorrect file position on Windows (but Linux is OK)

Martin Panter added the comment: Is this a duplicate of Issue 26016? -- nosy: +martin.panter ___ Python tracker ___

[issue28804] file tell() report incorrect file position on Windows (but Linux is OK)

liugang added the comment: Python 3.5.2 (v3.5.2:4def2a2901a5, Jun 25 2016, 22:18:55) [MSC v.1900 64 bit (AMD64)] on win32 Type "copyright", "credits" or "license()" for more information. >>> f = open('e:\\1.txt') >>> f.readline() '1\n' >>> f.tell() 340282367000166625996085689099021713410 >>>

[issue28804] file tell() report incorrect file position (Windows, Linux is OK)

New submission from liugang: D:\Python35\python.exe "D:\PyCharm Community Edition 2016.3\helpers\pydev\pydevconsole.py" 8871 8872 PyDev console: starting. import sys; print('Python %s on %s' % (sys.version, sys.platform)) sys.path.extend(['C:\\Users\\liugang10\\PycharmProjects\\untitled',

[issue28758] UnicodeDecodeError: 'gbk' codec can't decode byte 0xab in position 74: illegal multibyte sequence

Steve Dower added the comment: For something as low level as os.popen you should read bytes and decode them manually with the correct encoding. If you use subprocess.Popen instead you can specify encoding="utf-8" in the call (on 3.6). Unfortunately, it's a very bad idea to rely on the default

[issue28777] Add asyncio.Queue __aiter__, __anext__ methods

Guido van Rossum added the comment: Also it's not clear that it's a good idea without more thought -- there's no way to end the loop on the producing side. -- ___ Python tracker

[issue28777] Add asyncio.Queue __aiter__, __anext__ methods

Guido van Rossum added the comment: This should be an upstream PR first (GitHub.com/python/asyncio). Also, too late for 3.6. -- versions: -Python 3.5, Python 3.6 ___ Python tracker

[issue24339] iso6937 encoding missing

John Helour added the comment: @mdk Big thanks for the checker. >Looks like your implementation is missing some codepoints, like "\t": > >>>> >print("\t".encode(encoding='iso6937')) > >[...] >UnicodeError: encoding with 'iso6937'

[issue28788] ConfigParser should be able to write config to a given filename, not only into file object

Changes by Terry J. Reedy : -- title: Feature request: ConfigParser should be able to write config to a given filename, not only into file object -> ConfigParser should be able to write config to a given filename, not only into file object

[issue28777] Add asyncio.Queue __aiter__, __anext__ methods

Changes by Terry J. Reedy : -- stage: -> test needed title: asinc iter queue -> Add asyncio.Queue __aiter__, __anext__ methods versions: +Python 3.6, Python 3.7 ___ Python tracker

[issue28763] Use en-dashes for ranges in docs

Terry J. Reedy added the comment: I checked the patch with Rietveld and all the changes are '-' to '--' in numeric ranges in text. LGTM. -- nosy: +terry.reedy stage: -> commit review ___ Python tracker

[issue24339] iso6937 encoding missing

John Helour added the comment: PEP8 compliant, added missing codepoints, utf-8 to \u rewrited -- Added file: http://bugs.python.org/file45647/iso6937.py ___ Python tracker

[issue28758] UnicodeDecodeError: 'gbk' codec can't decode byte 0xab in position 74: illegal multibyte sequence

Terry J. Reedy added the comment: I don't see what this has to do with Python. Perhaps out Windows experts can, or can ask for more info. The last I knew, code page 65001 was buggy, but that is not a Python issue. -- components: +Windows nosy: +paul.moore, steve.dower, terry.reedy,

[issue28625] multiprocessing.Pool.imap swallows exceptions thrown by generators

Davin Potts added the comment: Closing this issue -- all further discussion moves to issue28699 -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker

[issue28696] imap from ThreadPool hangs by an exception in a generator function

Davin Potts added the comment: Closing this issue -- all further discussion moves to issue28699 -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker

[issue28699] Imap from ThreadPool behaves unexpectedly

Davin Potts added the comment: Attaching promised crude tests. -- Added file: http://bugs.python.org/file45646/issue_28699_repro.py ___ Python tracker

[issue28699] Imap from ThreadPool behaves unexpectedly

Davin Potts added the comment: @xiang.zhang: Nice catch -- thank you for pointing out the additional issue that arises when trying to provoke the issue twice in a row. The module attribute `job_counter` helped, in this situation, point out what might have otherwise been overlooked. I didn't

[issue28739] PEP 498: docstrings as f-strings

Terry J. Reedy added the comment: Much of this discussion seems to duplicate and effectively re-open of #25179, wherein it was decided/accepted that true, non-degenerate, non-trivial, non-constant, f-strings that actually do formatting are not constants and do not and should not become

[issue28518] execute("begin immediate") throwing OperationalError

Big Stone added the comment: rewording of sqlite documentation: http://www.sqlite.org/src/info/a4205a83e4ed977a -- ___ Python tracker ___

[issue28518] execute("begin immediate") throwing OperationalError

Big Stone added the comment: Comment kindly provided by D. Richard Hipp himself: " I don't have a login for the python bug tracker so I cannot comment there. But I think I see the problem. This is as Aviv Polivoda remarks at https://bugs.python.org/issue28518#msg279808 I think this is a

[issue28288] Expose environment variable for Py_Py3kWarningFlag

Serhiy Storchaka added the comment: PYTHON3WARNINGS looks as Python 3 variant of PYTHONWARNINGS. -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue28781] On Installation of 3.5 Python get error message

Steve Dower added the comment: I was hoping that Repair wouldn't be an option after doing that cleaning. Maybe try uninstalling through Programs and Features, then run those commands again, go into the places you installed it and delete the files, and then run a fresh install. If you still

[issue28518] execute("begin immediate") throwing OperationalError

Serhiy Storchaka added the comment: Here is a patch that allows executing "begin immediate" explicitly with any isolation_level. I don't know what behavior is more preferable. -- Added file: http://bugs.python.org/file45644/sqlite-explicit-begin.patch

[issue28754] Argument Clinic for bisect.bisect_left

Julien Palard added the comment: Quoting @martin > * bisect_right(a, x[, lo[, hi]]) -> index > This signature is removed. I think removing it is reasonable, because pydoc > can extract the proper signature from the Arg Clinic metadata. In fact, http://docs.python.org/howto/clinic.html, bullet

[issue8145] Documentation about sqlite3 isolation_level

Changes by Terry J. Reedy : -- nosy: -terry.reedy ___ Python tracker ___ ___

[issue28802] Python 3.6.0b4 Reports ncurses present in Cygwin but fails to build for cygwin

Changes by Berker Peksag : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Fix curses module compilation with ncurses6 ___ Python tracker

[issue28802] Python 3.6.0b4 Reports ncurses present in Cygwin but fails to build for cygwin

New submission from Masayuki Yamamoto: We're discussing a cause of this issue at #25720. -- nosy: +masamoto ___ Python tracker ___

[issue28288] Expose environment variable for Py_Py3kWarningFlag

Berker Peksag added the comment: Roy's patch looks good to me in general. Benjamin, as the RM of 2.7, do you have any objections? -- nosy: +benjamin.peterson ___ Python tracker

[issue28733] Show how to use mock_open in modules other that __main__

Berker Peksag added the comment: Thanks for the report and for the patch. I think expanding the "Where to patch" [1] section would be better. We can then refer to it from the mock_open() documentation. [1] https://docs.python.org/3.6/library/unittest.mock.html#where-to-patch --

[issue28738] Document SIGBREAK as argument for signal() under Windows.

Berker Peksag added the comment: Thanks for the report and for the patch, Wojtek! -- nosy: +berker.peksag resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.5 ___ Python tracker

[issue28738] Document SIGBREAK as argument for signal() under Windows.

Roundup Robot added the comment: New changeset dddce0f539dd by Berker Peksag in branch '3.5': Issue #28738: Document SIGBREAK as an acceptable value on Windows https://hg.python.org/cpython/rev/dddce0f539dd New changeset 43856eb83dc1 by Berker Peksag in branch '3.6': Issue #28738: Merge from

[issue28795] Misleading stating, that SIGINT handler is installed by default

Jan Velecký added the comment: That's good. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28801] configparser: before_get() method of class Interpolation has positional 'parser' parameter that is not used.

Changes by R. David Murray : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue28786] Warnings in Misc/NEWS

Changes by SilentGhost : -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue28689] OpenSSL 1.1.0c test failures

Charalampos Stratakis added the comment: Tested this in Fedora Rawhide virtual machine, where the fix for the problematic openssl commit was backported, and now the tests hang at test_poplib. Exception in thread Thread-982: Traceback (most recent call last): File

[issue28803] Python 3.6.0b4 Reports ncurses present in Cygwin but fails to build for Cygwin

Changes by Berker Peksag : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Python 3.6.0b4 Reports ncurses present in Cygwin but fails to build for cygwin ___ Python tracker

[issue28803] Python 3.6.0b4 Reports ncurses present in Cygwin but fails to build for Cygwin

Changes by Richard S. Gordon : -- components: Build nosy: rigordo priority: normal severity: normal status: open title: Python 3.6.0b4 Reports ncurses present in Cygwin but fails to build for Cygwin versions: Python 3.6 ___

[issue28796] FIX warnings in documentation build

Roundup Robot added the comment: New changeset f16f0500b49b by Berker Peksag in branch 'default': Issue #28796: Silence Sphinx warnings https://hg.python.org/cpython/rev/f16f0500b49b -- nosy: +python-dev ___ Python tracker

[issue28796] FIX warnings in documentation build

Berker Peksag added the comment: Thanks! -- nosy: +berker.peksag resolution: -> fixed stage: -> resolved status: open -> closed type: -> behavior ___ Python tracker

[issue28518] execute("begin immediate") throwing OperationalError

Aviv Palivoda added the comment: There are already a few test's that start a transaction explicitly: In dbapi.SqliteOnConflictTests CheckOnConflictRollbackWithExplicitTransaction, CheckOnConflictAbortRaisesWithExplicitTransactions which set ``isolation_level = None``. On the other hand in

[issue28802] Python 3.6.0b4 Reports ncurses present in Cygwin but fails to build for cygwin

Changes by Richard s. Gordon : -- nosy: eclectic9509 priority: normal severity: normal status: open title: Python 3.6.0b4 Reports ncurses present in Cygwin but fails to build for cygwin ___ Python tracker

[issue28793] Copy-paste error in collections.abc docs for AsyncGenerator

Berker Peksag added the comment: Thanks! -- assignee: -> docs@python components: +Documentation nosy: +berker.peksag, docs@python resolution: -> fixed stage: -> resolved status: open -> closed type: -> behavior ___ Python tracker

[issue28793] Copy-paste error in collections.abc docs for AsyncGenerator

Roundup Robot added the comment: New changeset 078c037b1571 by Berker Peksag in branch '3.6': Issue #28793: Fix c/p error in AsyncGenerator documentation https://hg.python.org/cpython/rev/078c037b1571 New changeset 0bf7c2d99bf1 by Berker Peksag in branch 'default': Issue #28793: Merge from 3.6

[issue28673] pyro4 with more than 15 threads often crashes 2.7.12

STINNER Victor added the comment: > I suggest thread_PyThread_start_new_thread() raise RuntimeError("can't start > thread: finalizing") Where *exactly*? Py_FinalizeEx() first calls wait_for_thread_shutdown() and *then* sets _Py_Finalizing to tstate. Does wait_for_thread_shutdown() complete on

[issue28800] Add RETURN_NONE bytecode instruction

STINNER Victor added the comment: > Do you want to add RETURN_NONE or RETURN_CONST? Or both? Only RETURN_NONE because on some corner cases it allow to avoid completely the None constant from code.co_consts and reduce the stack size. I'm not sure that I want to start taking the same road of

[issue28800] Add RETURN_NONE bytecode instruction

STINNER Victor added the comment: Results of performance 0.5.0 on speed-python: haypo@speed-python$ python3 -m perf compare_to -G --min-speed=3 2016-11-23_19-34-default-3d660ed2a60e.json patch.json Slower (3): - spectral_norm: 265 ms +- 2 ms -> 277 ms +- 7 ms: 1.04x slower -

[issue28673] pyro4 with more than 15 threads often crashes 2.7.12

INADA Naoki added the comment: This script can cause deadlock on Python 3.6. 1. Other threads can register traceback to sys module after sys module dict is cleaned up. 2. In Py_Finalize, __del__ method of arbitrary object in the traceback can be called. 3. The __del__ method calls

[issue28754] Argument Clinic for bisect.bisect_left

Martin Panter added the comment: Taking the first function, bisect_right(), as an example, I see these differences: * bisect_right(a, x[, lo[, hi]]) -> index This signature is removed. I think removing it is reasonable, because pydoc can extract the proper signature from the Arg Clinic

[issue8145] Documentation about sqlite3 isolation_level

Florian Schulze added the comment: The documentation patch is a definite improvement. -- nosy: +fschulze ___ Python tracker ___

[issue28801] configparser: before_get() method of class Interpolation has positional 'parser' parameter that is not used.

Wolfgang Maier added the comment: > Ah. Something like self._interpolation.before_get(self, section, option, > value, d) could be better written as > self._interpolation.before_get(parser=self, ...) Yep, that's roughly what I was trying to explain. > I still don't grock the apparent 'get()'

[issue28785] Clarify the behavior of NotImplemented

Martin Panter added the comment: Correct, I meant to say the first fallback is the other call. BTW your suggested text might hold for __eq__(), but for __ne__(), returning NotImplemented seems to bypass the “not a.__eq__(b)” fallback. -- ___ Python

[issue28754] Argument Clinic for bisect.bisect_left

STINNER Victor added the comment: Martin: "Victor, what changes to the doc strings are you talking about?" See attached check_bisect_doc.py script. Before: --- === bisect_right === bisect_right(a, x[, lo[, hi]]) -> index Return the index where to insert item x in list a, assuming a is sorted.

[issue28754] Argument Clinic for bisect.bisect_left

Martin Panter added the comment: Victor, what changes to the doc strings are you talking about? Adding descriptions of the parameters, maybe? Other than that they look very similar to me. I haven’t looked closely, but the Python doc strings have been updated at least once more than the C doc

[issue28801] configparser: before_get() method of class Interpolation has positional 'parser' parameter that is not used.

Richard Prosser added the comment: Ah. Something like self._interpolation.before_get(self, section, option, value, d) could be better written as self._interpolation.before_get(parser=self, ...) - but that would require keyword arguments to be used throughout. I still don't grock the apparent

[issue8145] Documentation about sqlite3 isolation_level

Berker Peksag added the comment: The patch needs to be updated to address changes in issue 10740 so I'm moving the stage field back to 'patch review'. -- stage: commit review -> patch review versions: +Python 3.7 ___ Python tracker

[issue28518] execute("begin immediate") throwing OperationalError

Berker Peksag added the comment: There is a patch in issue 8145 to improve that part of the documentation. It would be great if you could take a look at it :) -- ___ Python tracker

[issue17870] Python does not provide PyLong_FromIntMax_t() or PyLong_FromUintMax_t() function

STINNER Victor added the comment: I guess that the main question is if all platforms supported by Python do support intmax_t? -- ___ Python tracker ___

[issue17870] Python does not provide PyLong_FromIntMax_t() or PyLong_FromUintMax_t() function

STINNER Victor added the comment: intmax_t-4.patch is a single combined patch for Mercurial. To see individual changes, see the GitHub pull request: https://github.com/python/cpython/pull/46/commits -- ___ Python tracker

[issue17870] Python does not provide PyLong_FromIntMax_t() or PyLong_FromUintMax_t() function

STINNER Victor added the comment: New attempt to support C intmax_t type, since Python 3.6 now supports a subset of C99: intmax_t-4.patch. Changes: Add support for C intmax_t type: Add new conversions functions for PyLong: PyLong_FromIntMax() PyLong_FromUIntMax()

[issue17870] Python does not provide PyLong_FromIntMax_t() or PyLong_FromUintMax_t() function

Changes by STINNER Victor : -- nosy: +benjamin.peterson ___ Python tracker ___ ___

[issue28801] configparser: before_get() method of class Interpolation has positional 'parser' parameter that is not used.

Richard Prosser added the comment: Thanks for the prompt reply. I still don't fully understand yet but there aren't any errors reported so I presume that it is OK. There is another related matter however: PyCharm (2016.2.3) indicates that a get() method signature does not match that of the

[issue28518] execute("begin immediate") throwing OperationalError

Florian Schulze added the comment: Ok, I reread https://docs.python.org/3/library/sqlite3.html#controlling-transactions several times now. I think it's confusing. I want explicit transaction handling, but ``isolation_level = None`` turns on "autocommit mode". Unfortunately I don't have

[issue22298] Lib/warnings.py _show_warning does not protect against being called with a file like object which is closed

Terry J. Reedy added the comment: In 3.6, the code in question is def _showwarnmsg_impl(msg): file = msg.file if file is None: file = sys.stderr if file is None: # sys.stderr is None when run with pythonw.exe: # warnings get lost

[issue28800] Add RETURN_NONE bytecode instruction

Serhiy Storchaka added the comment: Do you want to add RETURN_NONE or RETURN_CONST? Or both? Adding new special opcodes can decrease the size of the code and increase performance of some cases. But it adds maintenance burden, increases the complexity of the compiler and peephole optimizer,

[issue28518] execute("begin immediate") throwing OperationalError

Berker Peksag added the comment: I haven't had a time to investigate this yet, but I don't think there is an issue with SQLite itself. Note that pysqlite behaves the same way since version 2.8.0 and I couldn't find a similar report in their issue tracker. Like Serhiy, I'm also a little

[issue28801] configparser: before_get() method of class Interpolation has positional 'parser' parameter that is not used.

Wolfgang Maier added the comment: Ah, that's kind of confusing at first! the 'self' in the method calls (like on line 796) refers to the ConfigParser instance and will be bound to the parser parameter. The first parameter, the 'self' in the interpolation method definition, is not provided as

[issue28800] Add RETURN_NONE bytecode instruction

STINNER Victor added the comment: I'm proposing this patch because I noticed that reducing the number of opcodes makes Python faster in my old registervm project: a fork of CPython which uses a register-based bytecode: http://faster-cpython.readthedocs.io/registervm.html I also plan to

[issue22298] Lib/warnings.py _show_warning does not protect against being called with a file like object which is closed

Julius Lehmann-Richter added the comment: Hey Wolfgang, thank you for the clarification. I would never write such code of course, I stumbled across this with a third-party program. I understand your point of view and I actually agree. I would not have even opened this report if it had not

[issue28800] Add RETURN_NONE bytecode instruction

Changes by Serhiy Storchaka : -- components: +Interpreter Core nosy: +rhettinger stage: -> patch review type: -> enhancement ___ Python tracker

[issue28801] configparser: before_get() method of class Interpolation has positional 'parser' parameter that is not used.

New submission from Richard Prosser: >From https://hg.python.org/cpython/file/3.5/Lib/configparser.py (for example): 358class Interpolation: 359"""Dummy interpolation that passes the value through with no changes.""" 360 361def before_get(self, parser, section, option, value, defaults):

[issue28800] Add RETURN_NONE

New submission from STINNER Victor: Attached patch adds a new bytecode instruction: RETURN_NONE. It is similar to "LOAD_CONST; RETURN_VALUE" but it avoids the need of adding None to constants of the code object. For function with an empty body, it reduces the stack size from 1 to 0. Example

[issue28800] Add RETURN_NONE bytecode instruction

Changes by STINNER Victor : -- title: Add RETURN_NONE -> Add RETURN_NONE bytecode instruction ___ Python tracker ___

[issue28782] SEGFAULT when running a given coroutine

STINNER Victor added the comment: Martin Richard: "Thank you all for fixing this so quickly, it's been done amazingly fast!" Even if I didn't write the commit a77756e480c2 which introduced the regression, I pushed it and so I felt responsible. It's a good motivation to fix it quickly. So

[issue28782] SEGFAULT when running a given coroutine

Martin Richard added the comment: Thank you all for fixing this so quickly, it's been done amazingly fast! -- ___ Python tracker ___

[issue22298] Lib/warnings.py _show_warning does not protect against being called with a file like object which is closed

Wolfgang Maier added the comment: Ah, I just found Issue607668, which discusses the changeset 2e7fe55c0e11 that introduced IOError suppression. The actual use case at the time was different and I have no idea whether it would still be a problem today. --

[issue22298] Lib/warnings.py _show_warning does not protect against being called with a file like object which is closed

Wolfgang Maier added the comment: Hi Julius, I guess it's a question of control and responsibilities. If you write a program that may issue warnings under some conditions, that program may, for example, be used with stderr redirected to a file. Now it is possible that file gets removed while

[issue28518] execute("begin immediate") throwing OperationalError

Aviv Palivoda added the comment: I searched in the sqlite tickets from something related to this issue and I couldn't find anything. I wanted to check the sqlite-users mailing list to see if anyone had already reported it but there is a problem in gmane archives. I tried to find a good way to

[issue22298] Lib/warnings.py _show_warning does not protect against being called with a file like object which is closed

Julius Lehmann-Richter added the comment: Hey Wolfgang, thank you for looking into this old one again ;) The argument you are making does not answer the original bug report though as far as I can see. My initial problem was not the AttributeError about the missing write but a ValueError

[issue28781] On Installation of 3.5 Python get error message

Mark Harris added the comment: Hi Steve, Thanks looking into this for me. I tried the below and ran the lines in cmd with admin privileges. Then I tried running repair again. I'm afraid when I type python in the command prompt it has the same message as before about missing python35.dll. I

[issue12844] Support more than 255 arguments

Serhiy Storchaka added the comment: No longer changes to Python/compile.c are needed. Here is a patch against 3.7 that just removes the limit of the number of passed arguments in Python/ast.c and adds tests. But still there is a limitation on the number of function parameters. It is caused

[issue28799] Drop CALL_PROFILE special build?

Changes by STINNER Victor : -- keywords: +patch Added file: http://bugs.python.org/file45637/remove_call_profile.patch ___ Python tracker

[issue28799] Drop CALL_PROFILE special build?

New submission from STINNER Victor: Python/ceval.c contains conditional code to compute statistics on function calls when CALL_PROFILE is defined. Extract of Misc/SpecialBuilds.txt: CALL_PROFILE Count the number of function calls executed. When this symbol is

[issue15533] subprocess.Popen(cwd) documentation

Wolfgang Maier added the comment: Before I forget again what I've gathered yesterday about this issue, here's a summary of the problem: When the the first element of args or the executable argument of subprocess.Popen does not specify an absolute path, the way the executable gets discovered

[issue28754] Argument Clinic for bisect.bisect_left

STINNER Victor added the comment: issue28754-4.diff does 3 things: * convert C code to Argument Clinic * change docstrings of the C code * change unit tests issue28754-5.diff doesn't touch tests, but still does 2 things. Sadly, I dislike the changes on docstrings because it makes the C

[issue28772] Bus error in Python 3.6.0beta

Changes by SilentGhost : -- resolution: not a bug -> third party stage: -> resolved ___ Python tracker ___

[issue28753] Clinic: Converting Your First Function is not up to date

STINNER Victor added the comment: issue28753.fastcall.diff LGTM. -- ___ Python tracker ___ ___