[issue22983] Cookie parsing should be more permissive

Changes by Waldemar Parzonka waldemar.parzo...@gmail.com: -- nosy: +Waldemar.Parzonka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22983 ___ ___

[issue22968] Lib/types.py nit: isinstance != PyType_IsSubtype

Greg Turner added the comment: Just added a commit message. -- Added file: http://bugs.python.org/file37349/fix_types_calculate_meta_v3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22968

[issue22968] Lib/types.py nit: isinstance != PyType_IsSubtype

Greg Turner added the comment: Here are some tests for this... first, some tests that pass right now and demonstrate, I think, correctness of the second batch of tests. -- Added file: http://bugs.python.org/file37350/test_virtual_metaclasses.patch

[issue22968] Lib/types.py nit: isinstance != PyType_IsSubtype

Greg Turner added the comment: And some analogous tests for types.py, which don't pass without fix_types_calculate_meta_v3.patch. -- Added file: http://bugs.python.org/file37351/test_virtual_metaclasses_in_types_module.patch ___ Python tracker

[issue22968] Lib/types.py nit: isinstance != PyType_IsSubtype

Greg Turner added the comment: And some analogous tests for types.py, which don't pass without fix_types_calculate_meta_v3.patch. -- Added file: http://bugs.python.org/file37352/test_virtual_metaclasses_in_types_module.patch ___ Python tracker

[issue22987] ssl module documentation: incorrect compatibility matrix

New submission from Kali Kaneko: The SSLv23 row that can be read in the socket creation section in the documentation for the ssl module looks incorrect: https://docs.python.org/2.7/library/ssl.html#socket-creation by my tests (with python 2.7.8) that row should read: yes no yes yes yes yes

[issue22987] ssl module documentation: incorrect compatibility matrix

Alex Gaynor added the comment: I agree this is a bug, but I believe the correct output is: no yes yes yes yes yes -- nosy: +alex, christian.heimes, dstufft, giampaolo.rodola, janssen, pitrou ___ Python tracker rep...@bugs.python.org

[issue22987] ssl module documentation: incorrect compatibility matrix

Antoine Pitrou added the comment: Alex is right. The current doc was valid for older OpenSSL versions, which sent a SSLv2 hello with SSLv23. Reference from the OpenSSL docs: If the cipher list does not contain any SSLv2 ciphersuites (the default cipher list does not) or extensions are

[issue22988] No error when yielding from `finally`

New submission from Felipe: This bug report is the opposite of issue #14718. The interpreter did not raise an error when it encountered a `yield` expression inside the `finally` part of a `try/finally` statement. My system's info: Python 3.4.2 (v3.4.2:ab2c023a9432, Oct 6 2014, 22:15:05)

[issue22988] No error when yielding from `finally`

Changes by Ethan Furman et...@stoneleaf.us: -- nosy: +ethan.furman, giampaolo.rodola, gvanrossum, haypo, pitrou, yselivanov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22988 ___

[issue22988] No error when yielding from `finally`

Guido van Rossum added the comment: There is no prohibition in the language against yield in a finally block. It may not be a good idea, but the behavior you see is all as it should be. -- ___ Python tracker rep...@bugs.python.org

[issue22989] HTTPResponse.msg not as documented

New submission from Paul Hartmann: HTTPResponse.msg is documented as a http.client.HTTPMessage object containing the headers of the response [1]. But in fact this is a string containing the status code: import urllib.request req=urllib.request.urlopen('http://heise.de') content =

[issue22988] No error when yielding from `finally`

R. David Murray added the comment: FIlipe, in case you hadn't noticed, the reason for the error in the other issue is that the generator was closed when it got garbage collected, and it ignored the close (executed a yield after the close). Thus the error message there is accurate and

[issue22989] HTTPResponse.msg not as documented

Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22989 ___ ___

[issue22987] ssl module documentation: incorrect compatibility matrix

Roundup Robot added the comment: New changeset 7af5d5493497 by Antoine Pitrou in branch '2.7': Fix #22987: update the compatibility matrix for a SSLv23 client. https://hg.python.org/cpython/rev/7af5d5493497 New changeset 9f03572690d2 by Antoine Pitrou in branch '3.4': Fix #22987: update the

[issue22988] No error when yielding from `finally`

Ethan Furman added the comment: Here's the excerpt from the docs: Yield expressions are allowed in the try clause of a try ... finally construct. If the generator is not resumed before it is finalized (by reaching a zero reference count or by being garbage

[issue22987] ssl module documentation: incorrect compatibility matrix

Changes by Antoine Pitrou pit...@free.fr: -- resolution: - fixed stage: - resolved status: open - closed versions: +Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22987

[issue22988] No error when yielding from `finally`

Felipe added the comment: Thanks for the clarification; sorry I misread issue #14718. I agree with Ethan's point. Though I would say Yield expressions are allowed anywhere in try ... except ... finally constructs. I'd also like to explicitly add a point about the exception-handling machinery

[issue22988] No error when yielding from `finally`

Changes by Guido van Rossum gu...@python.org: -- nosy: -gvanrossum ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22988 ___ ___ Python-bugs-list

[issue11101] plistlib has no graceful way of handing None values

Changes by Matt Hansen hanse...@me.com: -- nosy: +Matt.Hansen ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11101 ___ ___ Python-bugs-list mailing

[issue16329] mimetypes does not support webm type

Jim Jewett added the comment: I interpreted Issue 15's closure as being about the distinction between Application/webm vs Video/webm, etc. As far as I understand it, the python stdlib doesn't actually care what the major Mime type is, or, frankly, even whether the definition makes sense. We

[issue21557] os.popen os.system lack shell-related security warnings

Demian Brecht added the comment: After discussion in Rietveld, the patch looks good to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21557 ___

[issue16329] mimetypes does not support webm type

Chris Rebert added the comment: WebM's docs use video/webm and never use an application/* type. See http://www.webmproject.org/docs/container/ They also specify audio/webm for audio-only content, but both use the same file extension, so associating .webm with video/webm seems quite reasonable

[issue22982] BOM incorrectly inserted before writing, after seeking in text file

Antoine Pitrou added the comment: This is a limitation more than a bug. When you seek to the start of the file, the encoder is reset because Python thinks you are gonna to write there. If you remove the call to `file.seek(0, io.SEEK_SET)`, things work fine. @Amaury, whence can only be zero

[issue22982] BOM incorrectly inserted before writing, after seeking in text file

Mark Ingram added the comment: It's more than a limitation, because if I call `file.seek(0, io.SEEK_END)` then the encoder is still reset, and will still write the BOM, even at the end of the file. This also means that it's impossible to seek in a text file that you want to append to. I've

[issue21557] os.popen os.system lack shell-related security warnings

R. David Murray added the comment: Since Raymond is the person who tends to object most strongly to warning boxes in the docs, let's get his opinion on this. I'm not sure that the warning box is necessary, the text may be sufficient. On the other hand, this *is* a significant insecurity

[issue22990] bdist installation dialog

New submission from Alan: The Select Python Installations dialog box contains the line Select the Python locations where distribution_name should be installed. If distribution_name is anything other than a very short string, the line is truncated, due to the following factors: - the line

[issue16329] mimetypes does not support webm type

Terry J. Reedy added the comment: Antoine Pitrou and Ethan Furman agreed on pydev that this should be applied. Chris, is the existing patch exactly what you think is needed? -- nosy: +terry.reedy stage: - commit review type: - enhancement versions: +Python 3.5 -Python 3.4

[issue16329] mimetypes does not support webm type

Terry J. Reedy added the comment: Does test_mimetypes (assuming it exists), have a test for the mapping, are is something needed? -- stage: commit review - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16329

[issue16329] mimetypes does not support webm type

Chris Rebert added the comment: Yes, the existing patch looks fine. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16329 ___ ___

[issue16329] mimetypes does not support webm type

Ezio Melotti added the comment: A while ago there was a discussion about updating the MIME registry on bug fix releases too, and I seem to remember people agreed it should be done. If this is indeed the case and the patch is accepted for 3.5, should it also be backported to 2.7 and 3.4?

[issue22991] test_gdb leaves the terminal in raw mode with gdb 7.8.1

New submission from Xavier de Gaye: This happens on archlinux. Annoying: the terminal becomes unusable unless you type blindly 'stty sane CTL-J', and the backspace key is still wrong. This does not happen with gdb 7.6.1. And this does not happen when running gdb with the 'mi' interpreter. The

[issue22992] Adding a git developer's guide to Mercurial to devguide

New submission from Demian Brecht: Coming out of a recent thread in python-dev, it was mentioned that adding a git developer's guide to mercurial may be beneficial to help lower the initial barrier of entry for prospective contributors

[issue22992] Adding a git developer's guide to Mercurial to devguide

Ezio Melotti added the comment: I have a few comments about the patch. About the markup: 1) you can specify the default highlight (bash) once at the top of the file, and just use :: afterwards instead of .. code-block::; 2) the used for some headers is inconsistent with the other files;

[issue22991] test_gdb leaves the terminal in raw mode with gdb 7.8.1

Changes by Ned Deily n...@acm.org: -- nosy: +dmalcolm ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22991 ___ ___ Python-bugs-list mailing list

[issue20692] Tutorial and FAQ: how to call a method on an int

Changes by Josh Rosenberg shadowranger+pyt...@gmail.com: -- nosy: +josh.r ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20692 ___ ___

[issue22992] Adding a git developer's guide to Mercurial to devguide

Berker Peksag added the comment: +The workflow of a developer might look something like this: a core developer or a contributor? It would be good to split core developer and contributor workflows. +# address review comments and merge +git checkout master +git merge issueA +git

[issue17852] Built-in module _io can loose data from buffered files at exit

Changes by Nikolaus Rath nikol...@rath.org: -- nosy: +nikratio ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17852 ___ ___ Python-bugs-list

[issue17852] Built-in module _io can loose data from buffered files at exit

Nikolaus Rath added the comment: Serhiy, I believe this still happens in Python 3.4, but it is harder to reproduce. I couldn't get Armin's script to produce the problem either, but I'm pretty sure that this is what causes e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771452#60.

[issue22968] Lib/types.py nit: isinstance != PyType_IsSubtype

Greg Turner added the comment: Fixed a trivial typo in test_virtual_metaclass_in_types_module.patch -- versions: +Python 3.5 Added file: http://bugs.python.org/file37356/test_virtual_metaclasses_in_types_module_v2.patch ___ Python tracker

[issue16893] Generate Idle help from Doc/library/idle.rst

Roundup Robot added the comment: New changeset 6db65ff985b6 by Terry Jan Reedy in branch '3.4': Issue #16893: For Idle doc, move index entries, copy no-subprocess section https://hg.python.org/cpython/rev/6db65ff985b6 New changeset feec1ea55127 by Terry Jan Reedy in branch '2.7': Issue #16893:

[issue3068] IDLE - Add an extension configuration dialog

Roundup Robot added the comment: New changeset 395673aac686 by Terry Jan Reedy in branch '2.7': Issue #3068: Document the new Configure Extensions dialog and menu entry. https://hg.python.org/cpython/rev/395673aac686 New changeset b099cc290ae9 by Terry Jan Reedy in branch '3.4': Issue #3068:

[issue3068] IDLE - Add an extension configuration dialog

Changes by Terry J. Reedy tjre...@udel.edu: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3068 ___ ___ Python-bugs-list

[issue22993] Plistlib fails on certain valid plist values

New submission from Connor Wolf: I'm using plistlib to process plist files produced by an iphone app. Somehow, the application is generating plist files with a absolute date value along the lines of `-12-30T00:00:00Z`. This is a valid date, and the apple plist libraries can handle this

[issue22993] Plistlib fails on certain valid plist values

Connor Wolf added the comment: Aaaand there is no markup processing. How do I edit my report? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22993 ___

[issue17852] Built-in module _io can loose data from buffered files at exit

Charles-François Natali added the comment: Serhiy, I believe this still happens in Python 3.4, but it is harder to reproduce. I couldn't get Armin's script to produce the problem either, but I'm pretty sure that this is what causes e.g.

[issue22993] Plistlib fails on certain valid plist values

Ned Deily added the comment: (Currently, it is not possible to edit a particular message in an issue. You could add a replacement comment to the issue and ask that the older message be delete.) This seems to be a problem date. As documented, plistlib converts plist dates to/from Python