[issue8979] OptParse __getitem__

Éric Araujo added the comment: Thanks for your report and your ideas for Python :) Some remarks: 1) New features have to target 3.2; 2.6 is the current stable version (only security and documentation fixes) and 2.7 is to be released really soon (end of the 2.x line); 2) Can you explain why

[issue8980] distutils.tests.test_register.RegisterTestCase.test_strict fails

Éric Araujo added the comment: I can’t reproduce with current svn checkout. -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-li

[issue8981] _struct.__version__ should be string, not bytes

Mark Dickinson added the comment: Yes, I agree that _struct.__version__ can die. Removed in r81937. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue1492704] distinct error type from shutil.move()

Changes by Éric Araujo : -- assignee: anthonybaxter -> tarek nosy: +merwok, tarek versions: +Python 3.2 -Python 2.7, Python 3.1 ___ Python tracker ___ _

[issue1076515] shutil.move clobbers read-only files.

Éric Araujo added the comment: Is this bug still relevant? -- assignee: -> tarek nosy: +merwok, tarek ___ Python tracker ___ ___ P

[issue8904] quick example how to fix docs

Tal Einat added the comment: Apparently so. Those instructions are thorough and to the point, just what I was looking for. Adding a mention of this somewhere obvious, such as the links I mentioned earlier, would be very helpful (this would have save me 30 minutes of futile searching). -

[issue3129] struct allows repeat spec. without a format specifier

Mark Dickinson added the comment: py3k patch committed (by Alexander) in r81895. Closing this; I would ideally like to see this change go into trunk too, but it's not essential and we're too close to the 2.7 release. -- resolution: accepted -> fixed status: open -> closed _

[issue2236] Distutils' mkpath implementation ignoring the "mode" parameter

Éric Araujo added the comment: Confirmed in trunk (2.7rc2), py3k (3.2), irrelevant for distutils2. Is it too late for 2.7? -- nosy: +merwok ___ Python tracker ___ __

[issue8904] quick example how to fix docs

Georg Brandl added the comment: Agreed. Added a "building" section to Documenting Python in r81393, will port to the other branches. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue8978] "tarfile.ReadError: file could not be opened successfully" if compiled without zlib

Lars Gustäbel added the comment: If you pass an explicit mode, the error message is more or less what you want: >>> tarfile.open("uga.tgz", mode="r:gz") [...] tarfile.CompressionError: gzip module is not available The way mode="r" detects which compression format is used is to open the file w

[issue7470] logger.StreamHandler emit encoding fallback is wrong

Christian Boos added the comment: Hello Vinay, I recently installed Python 2.6.5, and I see this buglet is also present there. When I reported the issue, I said 2.6 worked and IIRC it must have been 2.6 or 2.6.1. I don't know if it's worth to backport the fix for 2.6.6, but just in case, I

[issue7470] logger.StreamHandler emit encoding fallback is wrong

Éric Araujo added the comment: Only security fixes and documentation fixes are allowed to go into stable branches. -- nosy: +merwok ___ Python tracker ___ __

[issue8972] subprocess.list2cmdline doesn't quote the & character

Jean-Paul Calderone added the comment: Thanks for reporting this issue. Can you attach a patch which adds a unit test covering this behavior and fixing the quoting rules? It would be very helpful in resolving this ticket. If implementing the whole thing is too much work, if you could just

[issue8980] distutils.tests.test_register.RegisterTestCase.test_strict fails

Arfrever Frehtes Taifersar Arahesis added the comment: You would have to install docutils. -- ___ Python tracker ___ ___ Python-bugs-l

[issue8572] httplib getheader() throws error instead of default

Changes by Éric Araujo : -- keywords: -easy nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue8980] distutils.tests.test_register.RegisterTestCase.test_strict fails

Éric Araujo added the comment: After converting docutils through 2to3 *sigh* and making it visible to 3.2, I get only one failure: NameError: global name 'RawInputs' is not defined The DistutilsSetupError (“The docutils package is needed.”) also happens with 2.7, although “pydoc2.7 docutils”

[issue3075] make minidom.toxml() encoding argument useful

Éric Araujo added the comment: Is this still relevant for 3.2? -- nosy: +merwok versions: +Python 3.3 -Python 2.6, Python 3.0 ___ Python tracker ___ _

[issue3075] make minidom.toxml() encoding argument useful

Changes by Éric Araujo : -- versions: +Python 3.2 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue459007] Document sys.path on Windows

Changes by Éric Araujo : -- assignee: georg.brandl -> d...@python nosy: +d...@python versions: +Python 3.2 -Python 3.0 ___ Python tracker ___ ___

[issue8980] distutils.tests.test_register.RegisterTestCase.test_strict fails

Arfrever Frehtes Taifersar Arahesis added the comment: 'python3.2 setup.py build' automatically uses 2to3. You should use docutils trunk. docutils-0.6 has many bugs in support for Python 3. I have docutils installed (using Portage, Gentoo's package manager) for Python 2.6, 2.7, 3.1 and 3.2 an

[issue8202] sys.argv[0] and python -m package

Nick Coghlan added the comment: Grr, in doing the Py3k forward port I found the hack based on the "-c" entry that I remembered (I had mentioned it *right there* in a comment in main.c, so I don't know how I missed it when first updating 2.7 - I suspect I got lost in the ifdef maze inside SetA

[issue8980] distutils.tests.test_register.RegisterTestCase.test_strict fails

Éric Araujo added the comment: Since I already had docutils for my system 2.6 version, I just copied it all and converted it for 3.2. I prefer not to use software that’s not available through my system package manager, but that’s hardly relevant here :) So, if the io import is fixed, I guess th

[issue8972] subprocess.list2cmdline doesn't quote the & character

Changes by Ezio Melotti : -- nosy: +ezio.melotti stage: -> unit test needed versions: +Python 2.7 -Python 2.5 ___ Python tracker ___ _

[issue8572] httplib getheader() throws error instead of default

Changes by Éric Araujo : -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8572] httplib getheader() throws error instead of default

Changes by Shashwat Anand : -- nosy: +l0nwlf ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8982] argparse docs cross reference Namespace as a class but the Namespace class is not documented

New submission from R. David Murray : I wanted to find out if Namespace supported lookup by subscripting (args['someopt']), but the docs are silent on what Namespace is. (The answer, by the way, appears to be "no"; there is a feature request for this in issue 8979). -- assignee: beth

[issue8979] OptParse __getitem__

Changes by R. David Murray : -- nosy: +bethard ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue7490] IGNORE_EXCEPTION_DETAIL should ignore the module name

Nick Coghlan added the comment: And done for 3.2 in r81944 (that checkin included a correction to the docs example which I backported to 2.7 in r81945) -- status: pending -> closed ___ Python tracker _

[issue8973] Inconsistent docstrings in struct module

Mark Dickinson added the comment: Here's a patch. Alexander, do you want to check it for sanity? -- keywords: +patch Added file: http://bugs.python.org/file17642/issue8973.patch ___ Python tracker

[issue8973] Inconsistent docstrings in struct module

Mark Dickinson added the comment: N.B. The patch doesn't fix the missing struct.Struct documentation issue; I'll look at that separately. -- ___ Python tracker ___

[issue8973] Inconsistent docstrings in struct module

Changes by Mark Dickinson : Added file: http://bugs.python.org/file17643/issue8973.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8973] Inconsistent docstrings in struct module

Changes by Mark Dickinson : Removed file: http://bugs.python.org/file17642/issue8973.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue8973] Inconsistent docstrings in struct module

Mark Dickinson added the comment: The docstrings need to be rewrapped to 72 characters; I'll do this once the wording is settled. -- ___ Python tracker ___

[issue8973] Inconsistent docstrings in struct module

Alexander Belopolsky added the comment: calcsize() still does not have signature in docstring. A nit: maybe follow calcsize() lead and say "format string fmt" rather than just "fmt". One more __doc__ mention: in Struct docstring, | __init__(...) | x.__init__(...) initializes x; see

[issue8973] Inconsistent docstrings in struct module

Mark Dickinson added the comment: r81947 fixes the missing struct.Struct entry in struct.help. (pydoc was relying on the inspect module to correctly guess the module for struct.Struct, and inspect was getting it wrong. Adding __all__ to the struct module saves inspect from having to guess.)

[issue8973] Inconsistent docstrings in struct module

Mark Dickinson added the comment: I also accidentally included the docstring changes in r81947; those were reverted in r81948. -- ___ Python tracker ___ ___

[issue8983] Docstrings should refer to help(name), not name.__doc__

New submission from Alexander Belopolsky : Inspired by issue issue8973, I did $ grep -in "see.*\.__doc__" Modules/*.c Surprisingly, there were not as many results as I feared. As I explained in the referenced issue, "See name.__doc__", while technically correct, is not user friendly. If yo

[issue8983] Docstrings should refer to help(name), not name.__doc__

Alexander Belopolsky added the comment: A couple more: $ grep -in "see.*\.__doc__" Lib/*.py Lib/doctest.py:1782:See doctest.__doc__ for an overview. Lib/inspect.py:162:See isfunction.__doc__ for attributes listing.""" an a really problematic Objects/typeobject.c:5529: "see x

[issue8973] Inconsistent docstrings in struct module

Mark Dickinson added the comment: Committed patch (with additional changes suggested by Alexander) in r81949. Only the __init__ doc issue remains. -- ___ Python tracker ___ ___

[issue8973] Inconsistent docstrings in struct module

Alexander Belopolsky added the comment: See issue #8983 for the the __init__ doc discussion since it is not specific to the struct module. -- ___ Python tracker ___

[issue8977] Globalize lonely augmented assignment

Demur Rumed added the comment: I've modified the patch to be less aggressive, as suggested by Nick at http://mail.python.org/pipermail/python-ideas/2010-June/007428.html As an aside, runtests.sh should have executable permissions -- Added file: http://bugs.python.org/file17644/diff.2

[issue8973] Inconsistent docstrings in struct module

Mark Dickinson added the comment: Apart from the pydoc __init__ issue, the Struct class documentation should probably be expanded a bit. At the moment, it's just: PyDoc_STRVAR(s__doc__, "Compiled struct object"); Alexander, interested in producing a patch? -- assignee: mark.dickinso

[issue8983] Docstrings should refer to help(name), not name.__doc__

Georg Brandl added the comment: I agree, help(obj) is the better advice. Would you prepare a patch? -- nosy: +georg.brandl ___ Python tracker ___ ___

[issue5094] datetime lacks concrete tzinfo impl. for UTC

Alexander Belopolsky added the comment: I have made my mind on subclassing timezone issue. I believe subclassing should not be allowed and here is the reason: The new datetime.timezone class is a very specific implementation of tzinfo interface. It guarantees that utcoffset(dt) and friends

[issue8983] Docstrings should refer to help(name), not name.__doc__

Alexander Belopolsky added the comment: Will do. -- assignee: d...@python -> belopolsky ___ Python tracker ___ ___ Python-bugs-list ma

[issue5094] datetime lacks concrete tzinfo impl. for UTC

Mark Dickinson added the comment: I agree it seems fine to disallow subclassing of timezone. (And if we decide, in the light of new information, that that was wrong, then it's easy to allow subclassing later; harder to disallow it.) +1 for 'UTC±HH:MM' for both tzname and __str__, too. I'll

[issue8977] Globalize lonely augmented assignment

Mark Dickinson added the comment: > As an aside, runtests.sh should have executable permissions. Doesn't it already? On my system (without having ever messed with any permissions as far as I can recall), I have: newton:py3k dickinsm$ ls -l runtests.sh -rwxr-xr-x 1 dickinsm staff 2168 28

[issue8972] subprocess.list2cmdline doesn't quote the & character

shypike added the comment: Added patch file for subprocess.py and test_subprocess.py. -- keywords: +patch Added file: http://bugs.python.org/file17645/list2cmdline_ampersand_fix.patch ___ Python tracker ___

[issue7261] Document 2.x -> 3.x round changes in "What's New" documents.

Mark Dickinson added the comment: Here's a patch. -- keywords: +patch Added file: http://bugs.python.org/file17646/issue7261.patch ___ Python tracker ___

[issue3129] struct allows repeat spec. without a format specifier

Terry J. Reedy added the comment: If you think of this as this as a bug fix, it could go into 2.7.1. If you think of it as an ambiguity elimination that should only go into a new version, fine with me. My main concern is getting 3.2 as clear, clear, and consistent as possible. Thanks for fini

[issue7261] Document 2.x -> 3.x round changes in "What's New" documents.

Changes by Mark Dickinson : -- stage: needs patch -> commit review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue3129] struct allows repeat spec. without a format specifier

Alexander Belopolsky added the comment: This is borderline enough that I am not comfortable making a call. If anyone speaks in support of backporting I'll do it. For 2.7 or 2.7.1. -- status: closed -> pending ___ Python tracker

[issue5094] datetime lacks concrete tzinfo impl. for UTC

Alexander Belopolsky added the comment: > +1 for 'UTC±HH:MM' for both tzname and __str__, too. It looks like I subconsciently allocated enough characters for this in the string buffer, so now this is a single character change. I'll do it with other changes (if any) before commit. --

[issue8857] socket.getaddrinfo needs tests

Antoine Pitrou added the comment: Testing the patch under a Windows XP Qemu virtual machine gives the following error. Works fine under 64-bit Linux. == ERROR: testGetaddrinfo (test.test_socket.GeneralModuleTests)

[issue3129] struct allows repeat spec. without a format specifier

Mark Dickinson added the comment: I don't think it's a good idea to make a change like this in a bugfix release, since it could break existing code (though admittedly code that probably isn't doing anything useful). It's not a huge thing: both the risk and the gain from making the change are

[issue8972] subprocess.list2cmdline doesn't quote the & character

Jean-Paul Calderone added the comment: Thanks. I'm not sure this is a correct change. And in fact, I would say that the current quoting of | is also incorrect. & and | (and ^ and perhaps several others) have special meaning to cmd.exe. list2cmdline is documented as applying the quoting rul

[issue8972] subprocess.list2cmdline doesn't quote the & character

Changes by Jean-Paul Calderone : -- components: +Library (Lib) stage: unit test needed -> ___ Python tracker ___ ___ Python-bugs-list

[issue8972] subprocess.list2cmdline doesn't quote the & character

Changes by Brian Curtin : -- nosy: +brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue8972] subprocess.list2cmdline doesn't quote the & character

Jean-Paul Calderone added the comment: http://www.autohotkey.net/~deleyd/parameters/parameters.htm#WINCRULES is a helpful reference, by the way. -- ___ Python tracker ___ __

[issue8983] Docstrings should refer to help(name), not name.__doc__

Alexander Belopolsky added the comment: Attaching issue8983.diff patch. I am a bit unsure about __init__ docstring change: 1. Are cases when help(type(x)) differs from help(x) important enough to distinguish in docstring? 2. Do we need a default docstring on __init__ at all? If so, should

[issue8469] struct - please make sizes explicit

Mark Dickinson added the comment: I've added sizes to the table, reordered some of the sections, and made a couple of other tweaks (like renaming the 'Objects' section to 'Classes') in r81957 (trunk) and r81955-81956 (py3k). I'll backport these changes to release26-maint and release31-maint;

[issue5094] datetime lacks concrete tzinfo impl. for UTC

Alexander Belopolsky added the comment: Attaching issue5094f.diff which implements 'UTC±HH:MM' and adds unit tests for more error cases. -- Added file: http://bugs.python.org/file17648/issue5094f.diff ___ Python tracker

[issue8857] socket.getaddrinfo needs tests

Giampaolo Rodola' added the comment: Does that mean has_ipv6() is broken maybe? I've just tested it against a Windows XP sp3 without IPv6 installed (socket.has_ipv6 returns True thought) and it doesn't fail. -- ___ Python tracker

[issue8469] struct - please make sizes explicit

Mark Dickinson added the comment: Merged to maintenance branches in r81959 (release26-maint) and r81960 (release31-maint). Closing. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: +Python 2.7, Python 3.1, Python 3.2

[issue8973] Inconsistent docstrings in struct module

Alexander Belopolsky added the comment: How does issue8973-Struct.diff look? -- Added file: http://bugs.python.org/file17649/issue8973-Struct.diff ___ Python tracker ___

[issue8973] Inconsistent docstrings in struct module

Mark Dickinson added the comment: Looks fine. I'd probably call the argument 'fmt' rather than 'format', for consistency. Please commit, with or without the 'format' -> 'fmt' change, as you choose. -- ___ Python tracker

[issue8973] Inconsistent docstrings in struct module

Alexander Belopolsky added the comment: Committed in r81961. Yes, I used "format" for consistency with the manual, but on the second thought consistency within help() is more important. -- ___ Python tracker ___

[issue8973] Inconsistent docstrings in struct module

Changes by Alexander Belopolsky : -- resolution: -> accepted stage: -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue8983] Docstrings should refer to help(name), not name.__doc__

Éric Araujo added the comment: 1. For old-style class instances, both help(i) and help(type(i)) give the help for the instance type, which is highly unhelpful IMO. Otherwise it seems than both C class instances and regular Python new-style class instances give the class doc for help(i). Summa

[issue8984] Python 3 doesn't register script arguments

New submission from Sworddragon : Python 3.1.2 hasn't any arguments except the file name in sys.argv[0]. For example: build.py test sys.argv[1] will be empty. I tried even the first example from the documentation 15.4 (optparse) but the filename is None. In Python 2.6.5 all is working fine. -

[issue8985] String format() has problems parsing numeric indexes

New submission from Germán L. Osella Massa : The str.format() method allows index lookup on an object that supports __getitem__(). However, negative indexes are not supported. Examples (using Python 2.6.5): >>> "{0[0]}".format([0, 1, 2]) '0' >>> "{0[-1]}".format([0, 1, 2]) Traceback (most rec

[issue8984] Python 3 doesn't register script arguments

Mark Dickinson added the comment: It's not entirely clear to me what issue you're reporting here: could you provide a short example script that exhibits the problem, and list the exact steps necessary to reproduce, along with actual and expected results? -- nosy: +mark.dickinson ___

[issue8985] String format() has problems parsing numeric indexes

Mark Dickinson added the comment: The behaviour is by design (I think), though perhaps the error messages could be improved. Are you asking for negative indices and extra space to be accepted? In that case this should be a feature request rather than a bug report. -- nosy: +eric.smi

[issue8979] OptParse __getitem__

Steven Bethard added the comment: Given that the one obvious way of using dict-style syntax given a Python object is to call vars(), I thing adding a __getitem__ is probably a bad idea. -- ___ Python tracker _

[issue8982] argparse docs cross reference Namespace as a class but the Namespace class is not documented

Steven Bethard added the comment: That's right, it doesn't support subscripting. The docs are silent on what namespace is mainly because I don't want to commit to anything other than an object with attributes. But that could be made clearer in the docs. -- versions: +Python 2.7 _

[issue8984] Python 3 doesn't register script arguments

Sworddragon added the comment: Examplescript test.py: import sys print(sys.argv[1]) Call this script now with an argument, for exmaple: test.py 1234 I expect to see the string 1234 in the console but Python 3 says "IndexError: list index out of range". With Python 2.6.5 I be able to see the

[issue8979] OptParse __getitem__

Bryan Ward added the comment: Thanks for your help and I apologize for the unnecessary ticket. I was unfamiliar with vars() which seems to accomplish what I wanted. -- status: open -> closed ___ Python tracker __

[issue8979] OptParse __getitem__

Éric Araujo added the comment: Don’t hesitate to propose future ideas to the python-ideas mailing list http://mail.python.org/mailman/listinfo/python-ideas -- resolution: -> rejected stage: -> committed/rejected ___ Python tracker

[issue8985] String format() has problems parsing numeric indexes

Éric Araujo added the comment: FYI, the version field is used to note versions where the bug will be fixed, not versions where it’s found. New features and bug fixes go to the dev branch (3.2), security and documentation fixes go to the stable branches (2.6 and 3.1). (2.7 is in release candid

[issue8984] Python 3 doesn't register script arguments

Éric Araujo added the comment: Can’t reproduce here: $ python3.1 -c "import sys; print(sys.argv[1])" 1234 1234 $ python3.1 --version Python 3.1.2 -- components: +Interpreter Core -Library (Lib) nosy: +merwok ___ Python tracker

[issue8984] Python 3 doesn't register script arguments

Mark Dickinson added the comment: Hmm. I don't see any difference between the two here (OS X 10.6). What platform are you on, and where did your copy of Python 3.1.2 come from? newton:~ dickinsm$ cat test.py import sys print(sys.argv[1]) newton:~ dickinsm$ python3.1 test.py 1234 1234 newton:

[issue8984] Python 3 doesn't register script arguments

Sworddragon added the comment: I'm using Windows XP Professional SP3. I downloaded Python 3.1.2 from this site. Even Python 3.0.1 hasn't worked. -- components: +Library (Lib) -Interpreter Core ___ Python tracker _

[issue8984] Python 3 doesn't register script arguments

Éric Araujo added the comment: 3.0 should not be used and does not get fixes. Can you try downloading Python again and testing? P.S. please do not change the component; Lib means “Python files under Lib/ in the source checkout”, but sys is a module built by the interpreter core. -- c

[issue8984] Python 3 doesn't register script arguments

Sworddragon added the comment: I have already installed Python 3.1.2 a second time. I have selected during the installation that the files shall be compiled into bytecode. -- components: +Library (Lib) -Interpreter Core ___ Python tracker

[issue8984] Python 3 doesn't register script arguments

Changes by Antoine Pitrou : -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8985] String format() has problems parsing numeric indexes

Eric Smith added the comment: get_integer uses the narrowest possible definition for integer indexes, in order to pass all other strings to mappings. >>> '{0[ 0 ]} {0[-1]}'.format({' 0 ': 'foo', '-1': 'bar'}) 'foo bar' Remember, it has to guess what type of lookup to do based on whether the v

[issue8984] Python 3 doesn't register script arguments

Mark Dickinson added the comment: I'm failing to reproduce this on Windows 7, too. It sounds as though you're starting the python script without an explict 'python'. What are your filetype associations for python scripts? i.e., what's the result of typing 'assoc py' at a console prompt? And

[issue8984] Python 3 doesn't register script arguments

Sworddragon added the comment: assoc .py .py=Python.File I tried this now with Ubuntu and Python 3.1.2 and all works fine. But under Windows XP it doesn't work. -- ___ Python tracker _

[issue8984] Python 3 doesn't register script arguments

Mark Dickinson added the comment: Okay, thanks. What does ftype Python.File give? -- ___ Python tracker ___ ___ Python-bugs-list ma

[issue8984] Python 3 doesn't register script arguments

Sworddragon added the comment: ftype Python.File Python.File="E:\Python31\python.exe" "%1" %* -- ___ Python tracker ___ ___ Python-bug

[issue8984] Python 3 doesn't register script arguments

Mark Dickinson added the comment: I've just found issue #7936, which looks like the same problem. I'm going to close this issue as a duplicate of that one; further discussion should be moved there. -- resolution: -> duplicate status: open -> closed superseder: -> sys.argv contains

[issue7936] sys.argv contains only scriptname

Mark Dickinson added the comment: Closed issue 8984 as a duplicate of this; merging nosy lists. Tom, did you ever find a solution to this problem? -- nosy: +Sworddragon, loewis, mark.dickinson, merwok ___ Python tracker

[issue7936] sys.argv contains only scriptname

Mark Dickinson added the comment: Here's a link to a similar discussion about Perl on Windows: http://community.activestate.com/forum-topic/problem-passing-arguments -- ___ Python tracker _

[issue8972] subprocess.list2cmdline doesn't quote the & character

shypike added the comment: A work-around could be that the caller puts double quotes around the individual elements of the sequence that need it. However, this won't work because list2cmdline doesn't handle backslash quoting properly. An element like r'"foo"' is translated to r'\"foo\"'. This

[issue7936] sys.argv contains only scriptname

Mark Dickinson added the comment: >From various other sites, and from experiments (thanks Eric Smith) it looks >like the associations reported by 'assoc' and 'ftype' aren't necessarily the >associations that are actually being used. Sworddragon: can you get any useful information out of the

[issue7936] sys.argv contains only scriptname

Eric Smith added the comment: I agree with Mark: there's probably nothing Python can do about this. It's almost certainly an error with how Python is being invoked. -- nosy: +eric.smith ___ Python tracker

[issue7936] sys.argv contains only scriptname

Eric Smith added the comment: That being said, it would be interesting to see what the registry key HKEY_CLASSES_ROOT\Python.File\shell\open\command contains. -- ___ Python tracker

[issue8469] struct - please make sizes explicit

Mads Kiilerich added the comment: Thanks for improving the documentation! A couple of comments for possible further improvements: I think it would be helpful to also see an early notice about how to achieve platform independence, versus the default of the local platform. And perhaps the desc

[issue8986] math.erfc OverflowError

New submission from geremy condra : In Python3.2, calling math.erfc with a value in [-27.2, -30) raises an OverflowError: math range error. This is inconsistent with the erfc function from scipy (scipy.special.erfc) as well as with the C99 function by the same name, both of which return 2. I susp

[issue8968] token type constants are not documented

Ilya Sandler added the comment: > * I would list them all in one directive, like this: Ok, done. Attaching the updated patch > There is no description in that directive. Best move part of the description above them in it. I am not sure I understand your request. Could you clarify? > NL a

  1   2   >