[issue27212] Doc for itertools, 'islice()' implementation have unwanted behavior for recipe 'consume()'

Changes by Serhiy Storchaka : -- assignee: docs@python -> rhettinger nosy: +rhettinger ___ Python tracker ___

[issue27212] Doc for itertools, 'islice()' implementation have unwanted behavior for recipe 'consume()'

New submission from alex0307: In the doc for itertools, the python implementation of islice() doesn't actually perform the iteration when given an empty slice (e.g. islice(it,3,3)). This is not the expected behavior for 'consume()' in the recipe given below, i.e. consume(it,3) couldn't

[issue22797] urllib.request.urlopen documentation falsely guarantees that a URLError will be raised on errors

Roundup Robot added the comment: New changeset 2d69d0419879 by Martin Panter in branch 'default': Issue #22797: Synchronize urlopen() doc string with RST documentation https://hg.python.org/cpython/rev/2d69d0419879 -- ___ Python tracker

[issue27211] Heap corruption via Python 2.7.11 IOBase readline()

Serhiy Storchaka added the comment: This bug was fixed for 3.x in issue18408. Maybe we should backport other Victor's fixes from this issue. Yet one possible bug -- using memcpy instead of memmove. The memory block can be resized without changing the address. -- nosy: +haypo,

[issue27211] Heap corruption via Python 2.7.11 IOBase readline()

Roundup Robot added the comment: New changeset afbd4473947a by Benjamin Peterson in branch '2.7': check the result of PyByteArray_Resize in readline() (closes #27211) https://hg.python.org/cpython/rev/afbd4473947a -- nosy: +python-dev resolution: -> fixed stage: -> resolved status:

[issue24225] Idlelib: changing file names

Ned Deily added the comment: I just tried to run IDLE from the command line as a (UNIX) user would. And then I grepped. :) -- ___ Python tracker ___

[issue27211] Heap corruption via Python 2.7.11 IOBase readline()

New submission from Benjamin Peterson: Guido Vranken on PSRT report: Python-2.7.11/Modules/_io/iobase.c iobase_readline(): 531 old_size = PyByteArray_GET_SIZE(buffer); 532 PyByteArray_Resize(buffer, old_size + PyBytes_GET_SIZE(b)); 533

[issue20567] test_idle causes test_ttk_guionly 'can't invoke "event" command: application has been destroyed' messages from Tk

Serhiy Storchaka added the comment: -To avoid interfering with other GUI tests, all GUI objects must be +To avoid interfering with other gui tests, all gui objects must be destroyed and Why "gui" is in lower case? -- ___ Python tracker

Re: Multiple inheritance, super() and changing signature

On Jun 3, 2016 7:12 PM, "Gregory Ewing" wrote: > > 4. It must not matter what order the methods in a super > chain are called. This is because you cannot predict > which method a given super call will invoke. It could > belong to a subclass of the class making the

[issue24225] Idlelib: changing file names

Terry J. Reedy added the comment: Thanks. Did you grep the whole repository for 'idlelib' or did you think to look for the latter two? -- ___ Python tracker

[issue27196] Eliminate 'ThemeChanged' warning when running IDLE tests

Terry J. Reedy added the comment: I closed #20567 after finishing what I intended to do 3 years ago. I decided make this a separate issue for trying Serhiy's suggestion of updata_idletasks. Pursuing 'no default root' is #24137. 3 other files also gave the warning, once, when run alone. 2

[issue20567] test_idle causes test_ttk_guionly 'can't invoke "event" command: application has been destroyed' messages from Tk

Terry J. Reedy added the comment: Using update_idletasks msg229182 is #27196; it succeeded in stopping ThemeChanged warnings. Using 'no-default-root' msg229201 is #24137. -- ___ Python tracker

[issue27196] Eliminate 'ThemeChanged' warning when running IDLE tests

Roundup Robot added the comment: New changeset 0207c6203f84 by Terry Jan Reedy in branch '3.5': Issue #27196: Stop 'application destroyed' warnings when running IDLE tests. https://hg.python.org/cpython/rev/0207c6203f84 New changeset 2d864ac472f0 by Terry Jan Reedy in branch 'default': Merge

Re: I'm wrong or Will we fix the ducks limp?

On 6/3/2016 7:31 PM, Steven D'Aprano wrote: On Sat, 4 Jun 2016 09:06 am, Sayth Renshaw wrote: I cant create a list with an append method pf.append(thing) in one go . Correct. You cannot append to a list until the list exists. Nor can you uppercase a string until the string exists: s =

Re: for / while else doesn't make sense

On Saturday, June 4, 2016 at 3:00:36 PM UTC+12, Steven D'Aprano wrote: > You can exit a loop because you have run out of items to process, or you can > exit the loop because a certain condition has been met. But why should they be expressed differently? item_iter = iter(items) while True

Re: for / while else doesn't make sense

On Saturday, June 4, 2016 at 2:22:18 PM UTC+12, Steven D'Aprano wrote: > and a loop with two or more exits a *trivially different* way: > > for x in seq: > do_something() > if condition: > break > if another_condition: > break But that loop has 3 exits, written in two

[issue25548] Show the address in the repr for class objects

Raymond Hettinger added the comment: Thanks Kushal. It looks like we had a race condition ;-) I'll assign it back after Nofar's work is in and reconciled. -- ___ Python tracker

[issue27198] Adding an assertClose() method to unittest.TestCase

Raymond Hettinger added the comment: FWIW, I find assertClose easy to misinterpret. At first, it looks like an assertion that a file is closed. And once you mentally pronounce it like "close something that is open", it is harder to make the jump to "close as in nearby". Also, I feed there

Re: for / while else doesn't make sense

On Sat, 4 Jun 2016 02:24 am, Lawrence D’Oliveiro wrote: > On Saturday, June 4, 2016 at 3:52:42 AM UTC+12, Rob Gaddi wrote: >> Lawrence D’Oliveiro wrote: >> >>> The reason why I don’t like this is that there are two ways out of the >>> Python for-statement, and they are written quite differently.

Re: Multiple inheritance, super() and changing signature

On Sat, 4 Jun 2016 11:06 am, Gregory Ewing wrote: > Nagy László Zsolt wrote: >> I do not use diamond shapes in my hierarchy, I guess that does not >> affect me. I may be wrong. > > If there are no diamonds, In Python 3, or Python 2 with new-style classes, there are ALWAYS diamonds when you use

Re: Catch exception with message?

On Sat, 4 Jun 2016 09:14 am, Piyush Verma wrote: > Generally we catch exception using > except Exception as e: > > But sometimes, we see same type of exception is present with different > message. That suggests that whoever wrote the code doesn't know what they're doing. Intentionally giving

Re: I'm wrong or Will we fix the ducks limp?

On Sat, 4 Jun 2016 09:06 am, Sayth Renshaw wrote: > I cant create a list with an append method pf.append(thing) in one go . Correct. You cannot append to a list until the list exists. Nor can you uppercase a string until the string exists: s = "hello world" s = s.uppercase() Nor can you add

[issue20567] test_idle causes test_ttk_guionly 'can't invoke "event" command: application has been destroyed' messages from Tk

Changes by Terry J. Reedy : -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed versions: +Python 3.6 ___ Python tracker

Re: Don't put your software in the public domain

On Sat, 4 Jun 2016 06:58 am, Nobody wrote: > OTOH, a Free software licence is unilateral; the author grants the user > certain rights, with the user providing nothing in return. That's not the case with the GPL. The GPL requires the user (not the end-user, who merely avails themselves of their

[issue20567] test_idle causes test_ttk_guionly 'can't invoke "event" command: application has been destroyed' messages from Tk

Roundup Robot added the comment: New changeset 813bb6a4c693 by Terry Jan Reedy in branch '3.5': Issue 20567: Revise idle_test/README.txt and some tests to match new advice. https://hg.python.org/cpython/rev/813bb6a4c693 New changeset d8e5e3da4d57 by Terry Jan Reedy in branch 'default': Issue

Re: for / while else doesn't make sense

On Sat, 4 Jun 2016 02:22 am, Lawrence D’Oliveiro wrote: > In Python you write a loop with one exit in one way, a loop with two exits > in a different way, and a loop with more than two exits in yet another > entirely different way. Can you say “cognitive burden”? Yes I can, but I don't see the

Re: Don't put your software in the public domain

On Sat, 4 Jun 2016 02:15 am, Lawrence D’Oliveiro wrote: > On Friday, June 3, 2016 at 9:53:47 PM UTC+12, Steven D'Aprano wrote: > >> A licence is something like a contract... > > A licence is quite different from a contract. A contract requires some > indication of explicit agreement by both

Re: I'm wrong or Will we fix the ducks limp?

On 6/3/2016 10:20 AM, Sayth Renshaw wrote: Very briefly because I hope to shot down eloquently. Python is beautiful and is supposed to be a duck typed language, Yes? Then if I create and assign to a new variable with a list action why does the duck not quack? It feels wrong to spend a line

Re: Don't put your software in the public domain

On Fri, 3 Jun 2016 11:14 pm, Michael Torrie wrote: > I'm not sure this is completely right. The GPL explicitly says one doesn't > have to agree to the GPL to use the software. The GPL only comes into > affect when distribution is involved. Yes, you're right, I was unclear. See

[issue27179] subprocess uses wrong encoding on Windows

Dāvis added the comment: > qprocess.exe (also to console) > quser.exe (also to console) these are broken (http://i.imgur.com/0zIhHrv.png) >chcp 1257 >quser USERNAME SESSIONNAME dƒvis console > chcp 775 > quser USERNAME

[issue27179] subprocess uses wrong encoding on Windows

Steve Dower added the comment: > so ANSI is the natural default for a detached process To clarify - ANSI is the natural default *for programs that don't support Unicode*. Unfortunately, since "Unicode" on Windows is an incompatible data type (wchar_t rather than char), targeting Unicode

[issue27202] make doctest fails on 2.7 release notes

Martin Panter added the comment: Since I stuck my neck out, I will say that this seems reasonable to me. We could probably still run doctest in the actual 2.7 branch to detect any errors there. -- stage: -> patch review versions: +Python 3.5 ___

[issue27203] Failing doctests in Doc/faq/programming.rst

Martin Panter added the comment: make -C Doc/ suspicious fails: WARNING: [faq/programming:1177] ".. testsetup:" found in ".. testsetup::" Suspicious check complete; look for any errors in the above output or in build/suspicious/suspicious.csv. If all issues are false positives, append that

[issue25738] http.server doesn't handle RESET CONTENT status correctly

Martin Panter added the comment: Ah, forget that bit about RESET_CONTENT. If we include Content-Length, it will probably be non-zero, which will be wrong. So your patch is better in that regard. -- ___ Python tracker

[issue27202] make doctest fails on 2.7 release notes

Jelle Zijlstra added the comment: Yes, I've been attempting to get that make to fully succeed. -- ___ Python tracker ___

[issue25738] http.server doesn't handle RESET CONTENT status correctly

Martin Panter added the comment: I suggest to drop the RESET_CONTENT exception. Content-Length: 0 is explicitly allowed by option a), and is not very different to the general case IMO. Content-Length was added here to help with buggy

Re: Multiple inheritance, super() and changing signature

Ben Finney wrote: With classes all inheriting ultimately from ‘object’ (as all Python 3 classes do, and as all current Python 2 classes should), mutliple inheritance inevitably places your classes in a diamond inheritance pattern. That's usually harmless, though, because object provides very

Re: Catch exception with message?

On 04Jun2016 04:44, Piyush Verma <114piy...@gmail.com> wrote: Generally we catch exception using except Exception as e: But sometimes, we see same type of exception is present with different message.Is there a way to capture same exception with message filtering? Please help me to do this.

Re: Don't put your software in the public domain

On Saturday, June 4, 2016 at 8:58:19 AM UTC+12, Nobody wrote: > On Fri, 03 Jun 2016 09:15:55 -0700, Lawrence D’Oliveiro wrote: > > >> [quoted text muted] > > > > A licence is quite different from a contract. A contract requires some > > indication of explicit agreement by both parties, a licence

[issue27198] Adding an assertClose() method to unittest.TestCase

Chris Barker added the comment: """w.r.t. error messages, a regular function that raises AssertionError with a nice message will be precisely as usable.""" sure -- I totally agree -- but that's not the current unittest API :-( where would you put it? How would people find it and know to use

Re: Multiple inheritance, super() and changing signature

Nagy László Zsolt wrote: I do not use diamond shapes in my hierarchy, I guess that does not affect me. I may be wrong. If there are no diamonds, there is no need to use super. Explicit inherited method calls, done correctly, will work fine. The only downside is that if your inheritance

[issue27202] make doctest fails on 2.7 release notes

Martin Panter added the comment: Ignore my message; I was thinking of something different :) I presume you are running something like the following, which seems to smoke-test the examples in the documentation: make -C Doc doctest -- ___ Python

[issue27202] make doctest fails on 2.7 release notes

Changes by Martin Panter : -- Removed message: http://bugs.python.org/msg267213 ___ Python tracker ___

[issue27202] make doctest fails on 2.7 release notes

Martin Panter added the comment: What failures are seeing, and what version of Sphinx are you using? Perhaps this is related to Issue 26638? -- nosy: +martin.panter ___ Python tracker

[issue26372] Popen.communicate not ignoring BrokenPipeError

Łukasz Langa added the comment: Thanks, I looked at this issue just today :) -- ___ Python tracker ___ ___

[issue24225] Idlelib: changing file names

Roundup Robot added the comment: New changeset 5dcc52d6829f by Ned Deily in branch 'default': Issue #24225: Fix additional renamed module references. https://hg.python.org/cpython/rev/5dcc52d6829f -- ___ Python tracker

Re: Catch exception with message?

Piyush Verma <114piy...@gmail.com> writes: > But sometimes, we see same type of exception is present with different > message.Is there a way to capture same exception with message > filtering? Please help me to do this. That's a nasty code smell. Why would you want your code to behave

[issue25738] http.server doesn't handle RESET CONTENT status correctly

Susumu Koshiba added the comment: Thanks, I've added some comments to the doc and updated the patch. -- Added file: http://bugs.python.org/file43182/issue25738_http_reset_content_02.patch ___ Python tracker

[issue24617] os.makedirs()'s [mode] not correct

Tommy Beadle added the comment: I've fixed the apostrophe issue by avoiding it's use. I've moved the text about the mode to mkdir and added a link to it from makedirs. -- Added file: http://bugs.python.org/file43180/0001-Issue-24617-Add-comment-for-os.makedirs-about-certai.patch

[issue27200] make doctest in CPython has failures

Jelle Zijlstra added the comment: Added a number of more specific issues with patches. I'll add more patches after the current ones are resolved. -- dependencies: +Failing doctests due to environmental dependencies in Lib/*lib.rst, Failing doctests in Doc/faq/programming.rst, Failing

Re: Multiple inheritance, super() and changing signature

Ian Kelly writes: > Except that since we're discussing design for multiple inheritance, > the positional argument "spam" is inappropriate. All arguments should > be passed by keyword; the DolorSitAmet.__init__ method cannot be > certain that LoremIpsum will be the next

[issue27209] Failing doctests in Library/email.*.rst

Changes by Jelle Zijlstra : -- assignee: docs@python components: Documentation files: doctests-email.patch keywords: patch nosy: Jelle Zijlstra, docs@python priority: normal severity: normal status: open title: Failing doctests in Library/email.*.rst versions:

[issue27210] Failing doctests due to environmental dependencies in Lib/*lib.rst

New submission from Jelle Zijlstra: The difflib test fails because "False" is close enough to "apple". The ftplib and nntplib tests rely on things downloaded from the web that are inherently variable. -- assignee: docs@python components: Documentation files: doctests-libs.patch

Re: Catch exception with message?

On Fri, Jun 3, 2016, at 19:14, Piyush Verma wrote: > Generally we catch exception using > except Exception as e: > > But sometimes, we see same type of exception is present with different > message.Is there a way to capture same exception with message > filtering? Please help me to do this. The

[issue27208] Failing doctests in Library/traceback.rst

New submission from Jelle Zijlstra: Updated to the output of current 3.6. -- assignee: docs@python components: Documentation files: doctests-traceback.patch keywords: patch messages: 267205 nosy: Jelle Zijlstra, docs@python priority: normal severity: normal status: open title: Failing

[issue26372] Popen.communicate not ignoring BrokenPipeError

Gregory P. Smith added the comment: the bot hasn't piped up with the changesets. these are the 3.5 and default fixes: remote: notified python-check...@python.org of incoming changeset 883cfb3e28f9 remote: notified python-check...@python.org of incoming changeset 78e81de6d447 --

[issue26372] Popen.communicate not ignoring BrokenPipeError

Gregory P. Smith added the comment: Lukas - cc'ing you just in case this bug is related to the asyncio subprocess race condition-ish problems you were talking about at pycon. -- nosy: +lukasz.langa ___ Python tracker

[issue27207] Failing doctests in Doc/whatsnew/3.2.rst

New submission from Jelle Zijlstra: Mostly missing imports, some bad syntax, and a few typos. This patch fixes most but not all errors. -- assignee: docs@python components: Documentation files: doctests-whatsnew-32.patch keywords: patch messages: 267203 nosy: Jelle Zijlstra,

[issue26372] Popen.communicate not ignoring BrokenPipeError

Changes by Gregory P. Smith : -- resolution: -> fixed stage: patch review -> commit review ___ Python tracker ___

[issue27206] Failing doctests in Doc/tutorial/

New submission from Jelle Zijlstra: Patch adds an import. -- assignee: docs@python components: Documentation files: doctests-tutorial.patch keywords: patch messages: 267202 nosy: Jelle Zijlstra, docs@python priority: normal severity: normal status: open title: Failing doctests in

[issue26373] asyncio: add support for async context manager on streams?

Roundup Robot added the comment: New changeset 883cfb3e28f9 by Gregory P. Smith in branch '3.5': Fixes Issue #26373: subprocess.Popen.communicate now correctly ignores https://hg.python.org/cpython/rev/883cfb3e28f9 New changeset 78e81de6d447 by Gregory P. Smith in branch 'default': merge from

[issue25738] http.server doesn't handle RESET CONTENT status correctly

R. David Murray added the comment: Well, the reason it makes sense to use send_error, or at least the reason I suspect a lot of people do it, is because then you don't have to call end_headers() yourself. So, acknowleding this, it might be worth mentioning in the docs that the body isn't

Re: Catch exception with message?

try: something except Exception as e: if e.args[0] == message_of_interest: handle_it else: raise On Fri, Jun 3, 2016 at 5:14 PM, Piyush Verma <114piy...@gmail.com> wrote: > Generally we catch exception using > except Exception as e: > > But sometimes, we see same type

[issue27205] Failing doctests in Library/collections.rst

New submission from Jelle Zijlstra: Mostly due to unspecified sorting order. The patch sorts a few tests and skips others that can't easily be sorted (e.g. most_common and str() output). -- assignee: docs@python components: Documentation files: doctests-collections.patch keywords:

[issue27204] Failing doctests in Doc/howto/

New submission from Jelle Zijlstra: Patch adds some imports, fixes doctests syntax, and skips Py2-only code. -- files: doctests-howto.patch keywords: patch messages: 267198 nosy: Jelle Zijlstra priority: normal severity: normal status: open title: Failing doctests in Doc/howto/ Added

[issue27203] Failing doctests in Doc/faq/programming.rst

New submission from Jelle Zijlstra: Patch attached. Added testsetup for the shared A variable and skipped doctests that rely on the return value of id(). -- files: faqdoctests.patch keywords: patch messages: 267197 nosy: Jelle Zijlstra priority: normal severity: normal status: open

[issue22797] urllib.request.urlopen documentation falsely guarantees that a URLError will be raised on errors

R. David Murray added the comment: Thanks, Alexander. -- resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.5 ___ Python tracker

[issue22797] urllib.request.urlopen documentation falsely guarantees that a URLError will be raised on errors

Roundup Robot added the comment: New changeset b4df20312b78 by R David Murray in branch 'default': Clean up urlopen doc string. https://hg.python.org/cpython/rev/b4df20312b78 -- ___ Python tracker

[issue24617] os.makedirs()'s [mode] not correct

Martin Panter added the comment: Thanks for the patch Tommy. One minor quirk that bugs me: *mode*'s gets marked up with an opening quote rather than an apostrophe. Perhaps we can change it to a Unicode apostrophe (*mode*’s). Another alternative would be: the octal representation of *mode*.

[issue19611] inspect.getcallargs doesn't properly interpret set comprehension code objects.

Jelle Zijlstra added the comment: Patch adding @cpython_only decorators to the tests. -- Added file: http://bugs.python.org/file43172/issue19611-decorators.patch ___ Python tracker

[issue25812] locale.nl_langinfo() can't decode value

R. David Murray added the comment: Thanks, Nina. We do have support in test.support for running a test with a specific locale (run_with_locale), so this could be turned into a unit test patch if you or someone else is willing to do that. -- nosy: +r.david.murray

[issue22257] PEP 432: Redesign the interpreter startup sequence

Nick Coghlan added the comment: I merged the current 3.6 dev branch into the BitBucket PEP 432 branch in my CPython sandbox. The attached patch is the diff between that branch and CPython default. All of the proposed changes here should only affect private APIs now, allowing this to be

[issue27202] make doctest fails on 2.7 release notes

New submission from Jelle Zijlstra: Running `make doctest` in the Doc/ repository of master fails on the 2.7 release notes. This patch excludes these files from `make doctest`, because it doesn't seem worth it to try to get these running in Python 3. -- assignee: docs@python

[issue16484] pydoc generates invalid docs.python.org link for xml.etree.ElementTree and other modules

R. David Murray added the comment: Thanks Sean and Kaushik. The final patch didn't apply to 2.7. If someone wants to port the patch I'll apply it, but I'm going to close the issue. -- resolution: -> fixed stage: test needed -> resolved status: open -> closed type: behavior ->

[issue15476] Index "code object" and link to code object definition

Martin Panter added the comment: Not sure why it doesn’t come up in the code review, but in diff --git a/Doc/reference/datamodel.rst b/Doc/reference/datamodel.rst index c0b4930..f34ba9f 100644 --- a/Doc/reference/datamodel.rst +++ b/Doc/reference/datamodel.rst @@ -847,8 +847,10 @@ Internal

[issue27198] Adding an assertClose() method to unittest.TestCase

Robert Collins added the comment: Future direction: hamcrest style matchers. You can read more about them in the context of unittest https://rbtcollins.wordpress.com/2010/05/10/maintainable-pyunit-test-suites/ and http://testtools.readthedocs.io/en/latest/for-test-authors.html#matchers -

[issue16484] pydoc generates invalid docs.python.org link for xml.etree.ElementTree and other modules

Roundup Robot added the comment: New changeset 64e7c8531131 by R David Murray in branch '3.5': #16484: Fix pydoc doc links to modules whose names are mixed case. https://hg.python.org/cpython/rev/64e7c8531131 New changeset 912b9aad0b45 by R David Murray in branch 'default': Merge: #16484: Fix

[issue27152] Additional assert methods for unittest

Robert Collins added the comment: I'm fine with these as a mixin - they are all very generic and unambiguously named. I'd marginally prefer the opt-in mixin over adding them to the base class. Ideally they'd be matchers, but since I haven't ported that upstream yet, thats asking for more

Re: I'm wrong or Will we fix the ducks limp?

> > def getsMeet(files=file_list): > > """Get a File or List of Files. > > > > From the list of files determine > > what meetings exist and prepare them > > to be parsed > > """ > > pyqFiles = [] > > for filename in sorted(file_list): > > pyqFiles =

Catch exception with message?

Generally we catch exception using except Exception as e: But sometimes, we see same type of exception is present with different message.Is there a way to capture same exception with message filtering? Please help me to do this. Regards, ~Piyush --

Re: I'm wrong or Will we fix the ducks limp?

> > pyqFiles = [] > > for filename in sorted(file_list): > > pyqFiles = pyqFiles.append(pq(filename=my_dir + filename)) > > > > return pyqFiles > > [snip] > > PS I am really having a lot of fun coding. > > To have even more fun, note that the above can be replaced by

Re: I'm wrong or Will we fix the ducks limp?

On Saturday, 4 June 2016 02:04:43 UTC+10, Michael Selik wrote: > > > That totally makes sense I was just double checking, had hoped I could > > create a variable assign it to a list and append in one stroke. > > > > In fact you can! It's called a "list comprehension" > > pyqFiles =

[issue24254] Make class definition namespace ordered by default

Changes by Eric Snow : Added file: http://bugs.python.org/file43169/deforder.diff ___ Python tracker ___

[issue24254] Make class definition namespace ordered by default

Changes by Eric Snow : Removed file: http://bugs.python.org/file43168/deforder.diff ___ Python tracker ___

[issue22558] Missing doc links to source code for Python-coded modules.

Terry J. Reedy added the comment: Great report. It appears that the remaining questions are subjective decisions for a core developer: what is the best link, if any, for a package; should the link also be last thing in the section. -- ___ Python

[issue24254] Make class definition namespace ordered by default

Eric Snow added the comment: Here's the full patch, including the addition of __definition_order__, tests, and docs. -- Added file: http://bugs.python.org/file43168/deforder.diff ___ Python tracker

[issue15476] Index "code object" and link to code object definition

Martin Panter added the comment: I haven’t tested, but maybe this will do what you want: .. index:: object; code, code object or .. index:: single: object; code single: code object -- ___ Python tracker

[issue27201] expose the ABI name as a config variable

New submission from Matthias Klose: Some python extensions provide/rely on support libraries which are shipped in addition to the extension module, and which depend on the Python ABI (version and ABI flags). talloc is such an example, and it currently uses the SOABI as the symbol version for

[issue24759] Idle: require tk 8.5 and ttk widgets, and drop unneeded code.

Terry J. Reedy added the comment: I saw the review comment about adding lines. I do not have 8.4 either, but I get the point: the startup version check does not not guard the unittests. After test.text_idle imports unittest and tkinter (as tk) (line 6), I will add if tk.TkVersion < 8.5:

[issue27162] Add idlelib.interface module

Terry J. Reedy added the comment: Import should fail if tk.TkVersion < 8.5. -- ___ Python tracker ___ ___

[issue27198] Adding an assertClose() method to unittest.TestCase

Chris Barker added the comment: Would that make folks more amenable to adding more "specialized" asserts? If so, then sure. I don't know that it takes a PEP (I hope not) but it would be good to have some guidance as to the direction we want unittest to take written down somewhere. --

[issue27140] Opcode for creating dict with constant keys

Demur Rumed added the comment: When is this intended to be merged? I've been waiting on this before updating the patch @ #27095 with fixes to other code review comments -- ___ Python tracker

[issue27198] Adding an assertClose() method to unittest.TestCase

R. David Murray added the comment: I raised the same point on that issue, and the answer as I understand it is that we want to change the API by making the assert methods independent of the rest of unit test, so I think Serhiy was seeing the mixin as a move in that general direction.

[issue27152] Additional assert methods for unittest

Chris Barker added the comment: Why a mixin rather than adding to TestCase? If they are useful they should be easy to find. Also, see Issue27198 for another possible new assert. -- nosy: +ChrisBarker ___ Python tracker

[issue16484] pydoc generates invalid docs.python.org link for xml.etree.ElementTree and other modules

R. David Murray added the comment: This patch looks good to me. Note that the reason for the basedir change is that the test would fail if run from a build directory which hadn't been installed. An implication of this is that 'doc_loc' is None most of the time when the other tests are run,

[issue27198] Adding an assertClose() method to unittest.TestCase

Chris Barker added the comment: thanks, that's Issue27152 if anyone's curious. Though I have no idea why you'd want it in a mixin, rather than just there. But sure, this could be "bundled" in with that. Perhaps it's time for a broader discussion / consensus about the future of the unittest

[issue22558] Missing doc links to source code for Python-coded modules.

Nathan Harold added the comment: I went through all the diffs in Rietveld, checking it against msg228576 as I went. There were (naturally) more source links added than there are in that list from 2014, and there were also many more files with slight header reorganizations for consistency.

[issue17888] docs: more information on documentation team

Berker Peksag added the comment: Thanks, Laura. I will commit issue17888_2.patch later today. -- ___ Python tracker ___

[issue24459] Mention PYTHONFAULTHANDLER in the man page

Berker Peksag added the comment: Thanks for the patch, Joshua. I did a quick review and it looks good to me. I will review and test it more carefully later today. -- ___ Python tracker

[issue27198] Adding an assertClose() method to unittest.TestCase

R. David Murray added the comment: On the name, I assumed it had something to do with files when I saw the issue title. I'm not sure that's enough of an argument against it, though. There's an issue where Serhiy is proposing a mixin with additional assert methods. If that has any traction

  1   2   3   >