[issue14578] importlib doesn't check Windows registry for paths

Amaury Forgeot d'Arc added the comment: importlib.h is not rebuilt on Windows, see issue15431. -- dependencies: +Cannot build importlib.h on Windows ___ Python tracker ___ _

[issue15431] Cannot build importlib.h on Windows

New submission from Amaury Forgeot d'Arc : On Windows, the _freeze_importlib tool is not built, so it's not possible to refresh the file Python/importlib.h, which makes development on the importlib very difficult on Windows. The Makefile contains the rules below, it's probably necessary to imp

[issue15295] Document PEP 420 namespace packages

Nick Coghlan added the comment: >From the import-sig discussions, this wasn't just about documenting PEP 420, >it was about finally bringing the full import system specification into the >language reference. (Now that it doesn't need to be loaded with caveats about >the old default import mec

[issue15295] Document PEP 420 namespace packages

Changes by Nick Coghlan : -- nosy: +larry, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue15376] Refactor the test_runpy walk_package support code into a common location

Chris Jerdonek added the comment: I created issue 15415 and uploaded a patch there with this issue in mind. test_runpy contains supporting _make_pkg() and _del_pkg() methods that, among other things, create and delete a temp directory. That logic would be better handled by a temp directory con

[issue14578] importlib doesn't check Windows registry for paths

Brian Curtin added the comment: I'm not sure what the deal is but I can't get the changes to apply (fitting Amaury's patch into _boostrap.py), meaning nothing I change to the _boostrap.py file changes how anything operates. I don't have much time to learn all of this stuff and make it work on

[issue13252] new decumulate() function in itertools module

Changes by Raymond Hettinger : -- assignee: -> rhettinger priority: normal -> low ___ Python tracker ___ ___ Python-bugs-list mailing

[issue15430] Improve filecmp documentation

Chris Jerdonek added the comment: Some comments on the patch: + The buffer size value which will be used to read the file contents. Defaults + to 8192 bytes. I would consider including the units for the value here (e.g. "The buffer size value in bytes..."). + When *shallow* flag is set

[issue15250] document that filecmp.dircmp comparisons are "shallow"

Chris Jerdonek added the comment: Thanks a lot for committing this for me Senthil. And thanks also for creating a separate issue for the other changes. I appreciate it. -- ___ Python tracker ___

[issue7578] Behavior of operations on a closed file object is not documented correctly

Kirubakaran Athmanathan added the comment: Looks like this was fixed in 3.3 in the commit 72890:a22d94547570 Should this issue be closed? -- nosy: +kirubakaran ___ Python tracker __

[issue15350] {urllib,urllib.parse}.urlencode.__doc__ is unclear

Changes by Senthil Kumaran : -- assignee: -> orsenthil ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue7003] finish documentation of user local paths

Changes by Senthil Kumaran : -- resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue7003] finish documentation of user local paths

Kirubakaran Athmanathan added the comment: This issue is present only in 3.0 and not in 3.2, 3.3 or 2.7. Since 3.0 is no longer maintained, I hope that this can be closed. Refer: http://docs.python.org/dev/library/site.html http://docs.python.org/release/3.2/library/site.html http://docs.pyth

[issue15250] document that filecmp.dircmp comparisons are "shallow"

Senthil Kumaran added the comment: This is taken care. Rest of documentation improvements could be dealt with in Issue15430. Thanks, Chris. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker

[issue15430] Improve filecmp documentation

New submission from Senthil Kumaran : filecmp.rst could see some improvements which are easy and useful too. It was discussed in Issue15250 and a patch is attached. -- assignee: orsenthil components: Documentation files: Issue15250.patch keywords: easy, patch messages: 166200 nosy: cjer

[issue15250] document that filecmp.dircmp comparisons are "shallow"

Roundup Robot added the comment: New changeset 3921d3c71e64 by Senthil Kumaran in branch '2.7': Issue #15250: Document that filecmp.dircmp compares files shallowly. Patch contributed by Chris Jerdonek. http://hg.python.org/cpython/rev/3921d3c71e64 -- __

[issue15250] document that filecmp.dircmp comparisons are "shallow"

Roundup Robot added the comment: New changeset f6ce142c2fce by Senthil Kumaran in branch '3.2': - Issue #15250: Document that filecmp.dircmp compares files shallowly. Patch contributed by Chris Jerdonek. http://hg.python.org/cpython/rev/f6ce142c2fce New changeset d2a49ee77b6f by Senthil Kumara

[issue9949] os.path.realpath on Windows does not follow symbolic links

Atsuo Ishimoto added the comment: Yet another patch to support symlink on Windows. -- nosy: +ishimoto Added file: http://bugs.python.org/file26487/issue9949.patch ___ Python tracker

[issue15232] email.generator.Generator doesn't mangle "From " lines in MIME preamble

R. David Murray added the comment: Same problem with the epilogue. Fixed both. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker _

[issue15232] email.generator.Generator doesn't mangle "From " lines in MIME preamble

Roundup Robot added the comment: New changeset b97f65f2298d by R David Murray in branch '3.2': #15232: correctly mangle From lines in MIME preamble and epilogue http://hg.python.org/cpython/rev/b97f65f2298d New changeset 80b81658455b by R David Murray in branch 'default': Merge #15232: correctl

[issue15250] document that filecmp.dircmp comparisons are "shallow"

Senthil Kumaran added the comment: Hi Chris, your patch looks good. I shall commit it now. The rest of the documentation changes can go in another patch. Thanks! -- ___ Python tracker

[issue14191] argparse doesn't allow optionals within positionals

Glenn Linderman added the comment: So my t18a.py wraps Argparse, because the externals are documented and I could understand that. Given enough time, I might be able to understand the internals too... it is just Python... Seems like the internals separate positionals and optionals into two s

[issue15250] document that filecmp.dircmp comparisons are "shallow"

Chris Jerdonek added the comment: Thanks, Senthil. I would prefer if you created a new issue in the tracker for your additional changes, and then committed your changes as part of that issue. By attribution, I was referencing the "Patch by Chris Jerdonek" which can go in the commit message

[issue15429] types.NoneType missing

R. David Murray added the comment: Thanks for the report. Fixed. -- nosy: +r.david.murray resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: +Python 3.3 ___ Python tracker __

[issue15429] types.NoneType missing

Roundup Robot added the comment: New changeset 84b577567fab by R David Murray in branch '3.2': #15429: Fix invalid mention of types.NoneType from None docs. http://hg.python.org/cpython/rev/84b577567fab New changeset c43d73277756 by R David Murray in branch 'default': Merge #15429: Fix invalid

[issue15429] types.NoneType missing

New submission from Anders Kaseorg : http://docs.python.org/py3k/library/constants.html#None says that None is the sole value type types.NoneType. However, NoneType was removed from the types module with Python 3. -- ___ Python tracker

[issue15429] types.NoneType missing

Changes by Anders Kaseorg : -- assignee: docs@python components: Documentation nosy: andersk, docs@python priority: normal severity: normal status: open title: types.NoneType missing type: behavior versions: Python 3.2 ___ Python tracker

[issue13720] argparse print_help() fails if COLUMNS is set to a low value

Steven Bethard added the comment: Definitely a bug here. Attached is a patch and a test, based on Russell Sim's suggestion, that should fix it. -- keywords: +patch versions: +Python 3.4 Added file: http://bugs.python.org/file26486/13720.patch ___ Py

[issue15271] argparse: repeatedly specifying the same argument ignores the previous ones

Steven Bethard added the comment: I'm going to close this issue, since argparse is doing what you've asked it to, even if that wasn't what you expected. But I think the documentation for this kind of thing could be improved. If you'd like to help document the workaround for your problem that

[issue15327] Argparse: main arguments and subparser arguments indistinguishable

Steven Bethard added the comment: If you'd like to help improve the documentation so that the workaround for your problem is more obvious, please contribute to Issue 15428. -- ___ Python tracker _

[issue15428] add "Name Collision" section to argparse docs

New submission from Steven Bethard : Several bugs (e.g. Issue 15327 and Issue 15271) have been filed suggesting that people aren't really clear on how argparse handles argument name collisions or how they can get it to do what they want. I think these problems could probably be solved by a "Na

[issue15327] Argparse: main arguments and subparser arguments indistinguishable

Steven Bethard added the comment: I don't think there's any easy way for argparse to automatically do what you want. However, there's a simple workaround - just use the dest= argument and specify two different destinations: >>> parser = argparse.ArgumentParser() >>> parser.add_argument('--ver

[issue9694] argparse required arguments displayed under "optional arguments"

Steven Bethard added the comment: I'm changing the title because I keep seeing duplicates. Documentation patches still welcome! -- title: argparse: Default Help Message Lists Required Args As Optional -> argparse required arguments displayed under "optional arguments" versions: +Pytho

[issue15336] Argparse required arguments incorrectly displayed as optional arguments

Changes by Steven Bethard : -- resolution: -> duplicate status: open -> closed superseder: -> argparse: Default Help Message Lists Required Args As Optional ___ Python tracker

[issue11176] give more meaningful argument names in argparse documentation

Steven Bethard added the comment: Thanks for working on this! I think keeping the first example as simple is possible is probably a good idea. And I didn't have time to read through the whole patch, but as far as I went, the pizza examples looked great. -- ___

[issue15125] argparse: positional arguments containing - in name not handled well

Steven Bethard added the comment: I'm sympathetic to the idea that '-' should be translated similarly for optional and positional arguments, but as you've noted, it would be a risky patch because it's already possible for people to use getattr on hyphenated arguments. So I think this isn't po

[issue15403] Refactor package creation support code into a common location

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue15423] Minidom tries to parse tags inside of

AliDD added the comment: Will give a try to some of them later. Thanks for info. -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue10854] Output .pyd name in error message of ImportError when DLL load fails

Kristján Valur Jónsson added the comment: Ok, the demo demo I added sucks, because I didn't demo the original problem (.pyd found but could not be loaded), but the point is, it displays the "name" and "path" attributes. They can be set, for example, if the module is found but cannot be loade

[issue15423] Minidom tries to parse tags inside of

Ezio Melotti added the comment: > Do you mean as parser with minidom.parseString() or stand alone? Standalone. > If second, than, result will be the sequence of handler calls instead of DOM. > This is not bad, but entirely different story. Indeed. If you want a tree you could try BeautifulS

[issue15423] Minidom tries to parse tags inside of

AliDD added the comment: @Ezio Melotti: Do you mean as parser with minidom.parseString() or stand alone? If second, than, result will be the sequence of handler calls instead of DOM. This is not bad, but entirely different story. -- ___ Python trac

[issue15271] argparse: repeatedly specifying the same argument ignores the previous ones

Steven Bethard added the comment: I don't think this is a bug. You've specified two arguments with the same destination, "foo". This means that argparse will parse the first one, assign it to the attribute "foo" and then parse the second one and assign it to the attribute "foo" again, overwri

[issue15360] Behavior of assigning to __dict__ is not documented

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue15420] issue6964 reminder

Changes by Florent Xicluna : -- nosy: -flox, loewis resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___ Python

[issue14191] argparse doesn't allow optionals within positionals

Steven Bethard added the comment: I created Issue 15427 for the parse_args documentation bug. So let's make this issue just about parsing intermixed arguments. Yes, if someone would like to provide a patch for this, please create a method "parse_intermixed_args" rather than adding a boolean f

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

New submission from Steven Bethard : >From http://bugs.python.org/issue14191#msg155202: ArgumentParser.parse_args(args=None, namespace=None) ... However, nowhere is the args= parameter explained. One example is given at the end of 15.4.4.6 showing the use of args= which apparently accepts a li

[issue15112] argparse: nargs='*' positional argument doesn't accept any items if preceded by an option and another positional

Steven Bethard added the comment: Your patch is a good start, but it needs to handle all the related situations, e.g. nargs='?' and the possibility of having more than one zero-length argument at the end. I believe the following patch achieves this. Please test it out. -- versions: +

[issue15147] Remove packaging from the stdlib

Éric Araujo added the comment: packaging (and related changes in sysconfig) have been removed. -- status: open -> closed ___ Python tracker ___ _

[issue11354] argparse: nargs could accept range of options count

Steven Bethard added the comment: The tests look like they're testing the right things, but the tests should instead be written like the rest of the argparse tests. For example, look at TestOptionalsNargs3 and TestPositionalsNargs2. You could write your tests to look something like those, e.g

[issue14156] argparse.FileType for '-' doesn't work for a mode of 'rb'

Steven Bethard added the comment: The fix looks right, but we definitely need a test. I tried to write one, but I'm not sure how to do this properly given how test_argparse redirects standard input and output (so that fileno() doesn't work anymore). I've attached my current (failing) attempt

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Daniel Swanson added the comment: No. When I try to open the file a small window entitled "Specify file encoding" pops up that says "The file's encoding is invalid in Python 3.x. Idle will convert it to UTF-8. What is the current encoding of the file?" followed by an entry widget that has "cp1

[issue14578] importlib doesn't check Windows registry for paths

Amaury Forgeot d'Arc added the comment: I don't have Windows, but here is an example of a WindowsRegistryImporter, written outside importlib (the script also contains a fake implementation of winreg, so I could test it...) Of course it needs to be rewritten to fit in _bootstrap.py; at least

[issue13252] new decumulate() function in itertools module

Ezio Melotti added the comment: I don't think this should go in itertools. It could go in the recipes at the bottom of the itertools doc, if you can provide some valid use cases (and possibly a patch too). -- nosy: +ezio.melotti stage: -> needs patch versions: +Python 3.4 -Python 3.

[issue15426] On a x86_64 Linux workstation, the build-from-source is borked.

Antoine Pitrou added the comment: This might (or might not) be a duplicate of issue1294959. -- nosy: +doko, eric.araujo, pitrou versions: +Python 2.7, Python 3.3 ___ Python tracker

[issue8538] Add FlagAction to argparse

Steven Bethard added the comment: On the off chance that someone was waiting for feedback from me, I'll say: (1) A simple boolean --foo/--no-foo action seems useful to me. I would probably call it BooleanOptionalAction rather than FlagAction. (Almost anything could be considered a "flag".) (

[issue15426] On a x86_64 Linux workstation, the build-from-source is borked.

New submission from Shocked Pancake : On a x86_64 Linux workstation, when building from source with ./configure --prefix=/usr --libdir=/usr/lib64 --enable-ipv6 --with-threads --enable-shared --doc-dir=/usr/doc/python --mandir=/usr/man, almost all library get installed in /usr/lib and not /usr

[issue15425] Another strange Tracebacks with importlib

New submission from Amaury Forgeot d'Arc : Two "easy" ways to get tracebacks which contain useless importlib._bootstrap rows: - When there is a syntax error in the imported module - On "import package.module", when top-level package cannot be imported $ ./python -c "import foo" Traceback (most

[issue14910] argparse: disable abbreviation

R. David Murray added the comment: Jonathan: we are in feature freeze right now preparing 3.3 for release, so you might want to ping the issue once 3.3 is out to remind us to do the checkin. -- nosy: +r.david.murray ___ Python tracker

[issue15350] {urllib,urllib.parse}.urlencode.__doc__ is unclear

Changes by Ezio Melotti : -- nosy: +ezio.melotti, orsenthil ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue15360] Behavior of assigning to __dict__ is not documented

Changes by Ezio Melotti : -- nosy: +ezio.melotti stage: -> needs patch type: -> enhancement ___ Python tracker ___ ___ Python-bugs-l

[issue15392] Create a unittest framework for IDLE

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue14910] argparse: disable abbreviation

Steven Bethard added the comment: Sorry, my mistake, the doc changes were already in the patch. I just checked them and they look good too. So everything's ready to commit. Thanks for your contribution! -- ___ Python tracker

[issue14910] argparse: disable abbreviation

Steven Bethard added the comment: I think it makes a lot of sense to allow people to disable abbreviations, so +1 on the feature request. The patch looked good. There was one typo - using "accept_abbrev" in the docstring instead of "allow_abbrev" as in the implementation, and I fixed that an

[issue15423] Minidom tries to parse tags inside of

Ezio Melotti added the comment: > That's why I try to use xml.dom.minidom to parse some HTML. Have you tried HTMLParser? -- nosy: +ezio.melotti resolution: -> invalid ___ Python tracker _

[issue15423] Minidom tries to parse tags inside of

R. David Murray added the comment: *xml*.dom.minidom parses only XML. The documentation mentions only xml, not html. I suppose that confusion could arise from the fact that that the w3c-dom API model can be provided by things that parse html as well. I'm not sure if it is worth adding a do

[issue15424] __sizeof__ of array should include size of items

Ludwig Hähne added the comment: Yes, it would be great if the change could be applied to 3.2 (and 2.7) but I guess not many people will be affected by the problem. BTW, I just submitted the contributor form. -- ___ Python tracker

[issue15420] issue6964 reminder

anatoly techtonik added the comment: > Please don't reopen issues. "Please don't ask for such silly stuff". You can understand the reason why this issue was opened, so why do you keep closing it if the "issue is not resolved"? The scope of this issue never changed, Martin. If you follow the

[issue15424] __sizeof__ of array should include size of items

Ludwig Hähne added the comment: Uses self->allocated instead of Py_SIZE as Martin suggested. -- Added file: http://bugs.python.org/file26480/array_sizeof_v2.patch ___ Python tracker ___

[issue15423] Minidom tries to parse tags inside of

AliDD added the comment: Document Object Model (DOM) Level 1 Specification at http://www.w3.org/TR/REC-DOM-Level-1/ states that "The Document Object Model provides a standard set of objects for representing HTML and XML documents" That's why I try to use xml.dom.minidom to parse some HTML. And

[issue15424] __sizeof__ of array should include size of items

Serhiy Storchaka added the comment: I think it should be applied to 3.2 too. -- nosy: +storchaka ___ Python tracker ___ ___ Python-bu

[issue11776] types.MethodType() params and usage is not documented

anatoly techtonik added the comment: Another 4 complains about missing references: http://stackoverflow.com/questions/1015307/python-bind-an-unbound-method -- ___ Python tracker __

[issue15423] Minidom tries to parse tags inside of

Martin v. Löwis added the comment: R. David is correct. The XML specification *clearly* defines that your XML document is ill-formed, since the closing tag for '' is '', which doesn't match. XML is not HTML: the XML parser must not treat the script element specially. -- nosy: +loewis

[issue15424] __sizeof__ of array should include size of items

Martin v. Löwis added the comment: Can you please submit a contributor form? -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-

[issue11776] types.MethodType() params and usage is not documented

anatoly techtonik added the comment: Still not documented.. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14489] repr() function link on the built-in function documentation is incorrect

Piotr Dobrogost added the comment: The wrong link is still at http://docs.python.org/library/functions.html -- ___ Python tracker ___ ___

[issue15424] __sizeof__ of array should include size of items

New submission from Ludwig Hähne : If sys.getsizeof is called on an array, the result doesn't include the size of the items: >>> from array import array >>> a = array("i", [0] * 10) >>> a.__sizeof__() 40 While this makes sense for a list, an array doesn't have separate referents that cou

[issue15397] Unbinding of methods

Stefan Mihaila added the comment: Andrew, thanks for creating a separate issue (the refleak was very rare and I thought I'd put it in the same place, but now I realize it was a bad idea). Richard, actually, the isinstance(self, type) check I mentioned earlier would have to be before the hasta

[issue10854] Output .pyd name in error message of ImportError when DLL load fails

Amaury Forgeot d'Arc added the comment: How it the new message better than "ImportError: No module named '_socket'"? -- ___ Python tracker ___ __

[issue15397] Unbinding of methods

Stefan Mihaila added the comment: Richard, yes, I think that would work, I didn't think of using f.__self__'s type. You might want to replace if self is not None and not isinstance(self, types.ModuleType): with if self is not None and not isinstance(self, types.ModuleType) \

[issue15423] Minidom tries to parse tags inside of

R. David Murray added the comment: I'm sorry, my phrasing there was awkward. I didn't mean "Why do you think this is a bug", I meant "I don't think this is a bug, am I missing something?" -- ___ Python tracker _

[issue15422] Get rid of PyCFunction_New macro

New submission from Andrew Svetlov : For now (3.3 beta) PyCFunction_New defined as macro calling PyCFunction_NewEx. To be compatible with PEP 384 (Defining a Stable ABI) Objects/methodobject.c has trampoline function named PyCFunction_New which calls PyCFunction_NewEx. This is only single usage

[issue15421] Calendar.itermonthdates OverflowError

New submission from Cédric Krier : itermonthdates fails when working on the last month of Here is a patch that catch the OverflowError. -- components: Library (Lib) files: calendar.patch keywords: patch messages: 166137 nosy: ced priority: normal severity: normal status: open title:

[issue15397] Unbinding of methods

Andrew Svetlov added the comment: Stefan, I've fixed refleak found by you in #15404. Thanks. -- ___ Python tracker ___ ___ Python-bug

[issue14578] importlib doesn't check Windows registry for paths

Brett Cannon added the comment: So it should end up in Lib/importlib/_bootstrap.py since it is directly part of how import works. The original code as found in Python 3.2 for PyWin_FindRegisteredModule() is referenced in Python/import.c and is implemented in PC/import_nt.c. You will want to c

[issue15419] distutils: build_py_2to3 should use a separate build directory

R. David Murray added the comment: Could you please be more specific about what you are trying to do and what error you are seeing? -- nosy: +r.david.murray ___ Python tracker

[issue15420] issue6964 reminder

Martin v. Löwis added the comment: IIUC, your request is not "should issue a warning", but "2to3 should make sure that the resulting code runs on Python 3". It is beyond the scope of 2to3 to provide such guarantees. Users are required to test the conversion result, as it cannot be perfect. S

[issue15420] issue6964 reminder

Changes by Martin v. Löwis : -- resolution: -> wont fix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue15420] issue6964 reminder

Martin v. Löwis added the comment: Please don't reopen issues. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue15041] tkinter documentation: update "see also" list

Andrew Svetlov added the comment: Add all recommended resources into seealso section. If it's ok I will commit it next week. -- keywords: +patch Added file: http://bugs.python.org/file26477/issue15041.diff ___ Python tracker

[issue15420] issue6964 reminder

anatoly techtonik added the comment: Florent: It is the same. "new" module just doesn't need replacement, because its functionality is in the language, therefore it is no different saying. -- ___ Python tracker _

[issue15420] issue6964 reminder

anatoly techtonik added the comment: My request is that after running 2to3 my code still doesn't work in Python 3. -- resolution: wont fix -> status: closed -> open ___ Python tracker

[issue15420] issue6964 reminder

Florent Xicluna added the comment: The documentation for porting is already clear about using "-3" switch. http://docs.python.org/dev/howto/pyporting.html#eliminate-3-warnings The argparse module is different because it is not in the stdlib in 2.6, and you can stay with optparse if you write c

[issue15420] issue6964 reminder

Martin v. Löwis added the comment: It does mean exactly that. 2to3 is not designed or intended to ever issue warnings. So if your request is that it should issue a warning, I'm closing it as "won't fix". -- resolution: -> wont fix status: open -> closed _

[issue15133] tkinter.BooleanVar.get() behavior and docstring disagree

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue15390] PEP 3121, 384 refactoring applied to datetime module

Andrew Svetlov added the comment: Too late for 3.3 -- nosy: +asvetlov versions: +Python 3.4 -Python 3.3 ___ Python tracker ___ ___ Py

[issue15402] Correct __sizeof__ support for struct

Andrew Svetlov added the comment: +1 for patch applying in 3.3 at least -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-lis

[issue10854] Output .pyd name in error message of ImportError when DLL load fails

Kristján Valur Jónsson added the comment: An example patch that aims to put the "name" and "path" in str() and repr() representations of ImportError. Output when _socket.pyd is not found: >>> import socket Traceback (most recent call last): File "", line 1, in File "D:\pydev\hg\cpython3\

[issue15420] issue6964 reminder

anatoly techtonik added the comment: Bottom line: The fact that 2to3 isn't capable to fix "import new" automatically doesn't mean it should not warn that this code should be fixed manually. -- ___ Python tracker

[issue15420] issue6964 reminder

anatoly techtonik added the comment: >From the user point of view that's the same as saying for optparse: Bottom line: move over to the argparse module *before* running 2to3. -- resolution: invalid -> ___ Python tracker

[issue15420] issue6964 reminder

Florent Xicluna added the comment: It was answered in the previous message by Georg, on the related issue: http://bugs.python.org/issue6964#msg93032 > Bottom line: move over to the types module *before* running 2to3. (the thread is very short, and clearly states that there's no bug) -

  1   2   >