[issue10716] Modernize pydoc to use CSS

Changes by Ron Adam : Removed file: http://bugs.python.org/file20183/css_v1.diff ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue10716] Modernize pydoc to use CSS

Changes by Ron Adam : Removed file: http://bugs.python.org/file20088/pydoc sample html files.zip ___ Python tracker ___ ___ Python-bugs-list m

[issue10716] Modernize pydoc to use CSS

Changes by Ron Adam : Removed file: http://bugs.python.org/file20081/defaultstyle.css ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue10716] Modernize pydoc to use CSS

Ron Adam added the comment: Here is a new diff which updates all the new pydoc pages to use the css file. The css file is simpler and cleaner. I also made a few adjustments to the url handler error handling, and changed the titles in the head sections so they say "Pydoc" instead of "Python"

[issue10803] ctypes: better support of bytearray objects

New submission from Markus F.X.J. Oberhumer : Python 3.2b2 does not properly support accessing bytearrays from ctypes, which makes dealing with large buffers somewhat unpleasant. A very first fix - a simple patch for the z_set() function - is given here. build/Python-3.2b2 $ quilt diff Index:

[issue10782] Not possible to cross-compile due to poor detection of %lld support in printf

Ben Gamari added the comment: Well, I'm not convinced that overriding config.cache is the best solution, but I am not really sure what else can be done. So far I've just been carrying a patch which changes configure.in, but this is clearly an awful hack. -- __

[issue5870] subprocess.DEVNULL

Ross Lagerwall added the comment: Here is a fairly simple patch that adds the subprocess.DEVNULL constant. -- keywords: +patch nosy: +rosslagerwall versions: +Python 3.3 -Python 2.7 Added file: http://bugs.python.org/file20215/5870_v1.patch ___ Pytho

[issue8013] time.asctime segfaults when given a time in the far future

Ned Deily added the comment: Thanks for the py3k patch. I am also attaching a refreshed patch for current 2.7. They both fix the segfaults when built and run on OS X 10.6 64-bit. Since the patches change timemodule to use asctime_r, which AFAICT is not used elsewhere in the standard librar

[issue10802] python3.2 AFTER b2 release has subprocess.Popen broken under colinux/windows

Gregory P. Smith added the comment: The only thing that could cause this error is if the Modules/_posixsubprocess.c subprocess_cloexec_pipe function fails either in the pipe2() call or if HAVE_PIPE2 is not defined one of the fcntl() calls. Can you look to see if HAVE_PIPE2 is defined? I susp

[issue10789] Lock.acquire documentation is misleading

Terry J. Reedy added the comment: I responded to the general questions on #8350. -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue8350] Document lack of support for keyword arguments in C functions

Terry J. Reedy added the comment: If there is no indication in the lib manual as to which parameter names and defaults are real and which are fake, then the safe guideline is to never use keywards for library functions and methods and always pass everything positionally. Slightly more compli

[issue8013] time.asctime segfaults when given a time in the far future

Andreas Stührk added the comment: Updated patch against py3k branch. -- nosy: +Trundle Added file: http://bugs.python.org/file20213/issue8013_py3k.diff ___ Python tracker ___ ___

[issue8350] Document lack of support for keyword arguments in C functions

Terry J. Reedy added the comment: I think that the warning that things are not always as they seem should be repeated in the front of the library manual where the pseudo-arg names are actual used, so the library manual stands on its own. In any case, I believe a lot of people use the lib ref

[issue10789] Lock.acquire documentation is misleading

Raymond Hettinger added the comment: I concur that the one warning is enough. Implementations have been given wide latitude in this regard. Even within CPython there is not much uniformity -- some funcs/methods don't accept keywords, some will disregard keywords, and others may have keyword

[issue10789] Lock.acquire documentation is misleading

Éric Araujo added the comment: Thanks for the correction Georg. In msg104113 (on #8350), I quoted http://docs.python.org/dev/reference/expressions#calls : “An implementation may provide built-in functions whose positional parameters do not have names, even if they are ‘named’ for the purpose

[issue10802] python3.2 AFTER b2 release has subprocess.Popen broken under colinux/windows

Changes by Georg Brandl : -- nosy: +georg.brandl priority: normal -> release blocker ___ Python tracker ___ ___ Python-bugs-list maili

[issue10802] python3.2 AFTER b2 release has subprocess.Popen broken under colinux/windows

Changes by Antoine Pitrou : -- assignee: -> gregory.p.smith nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailin

[issue8350] Document lack of support for keyword arguments in C functions

Raymond Hettinger added the comment: This is an implementation detail specific to CPython and subject to change. I'm -1 on documenting it for every function/method and thereby making it part of the language spec. We've lived without this spec for almost twenty years, so I'm inclined to think

[issue10802] python3.2 AFTER b2 release has subprocess.Popen broken under colinux/windows

New submission from kai zhu : i have 2 debian i386 unstable distros. 1) python3.2 (latest hg) running under vps @ linode.com seems ok 2) python3.2 (latest hg) running under colinux (in windows xp) breaks *NOTE 3) python3.2 (release b2) works fine under colinux pub...@colinux: python3.2 Python 3

[issue8350] Document lack of support for keyword arguments in C functions

Georg Brandl added the comment: Yes. It's still an important detail; the explanation could say, "In CPython, this function does not take keyword args" and furthermore it's not really clear to me how much of the library reference applies to all Python implementations anyway. --

[issue8350] Document lack of support for keyword arguments in C functions

Antoine Pitrou added the comment: > Hmm, it may indeed be the best option to add a new directive option to > say "this function does not take keyword args". It would result in > some form of unobtrusive but noticeable output in HTML. Isn't it kind of a CPython-specific detail, though? ---

[issue8350] Document lack of support for keyword arguments in C functions

Georg Brandl added the comment: Hmm, it may indeed be the best option to add a new directive option to say "this function does not take keyword args". It would result in some form of unobtrusive but noticeable output in HTML. It is a bit of an effort to add it everywhere it's necessary, but

[issue4662] posix module lacks several DeprecationWarning's

Benjamin Peterson added the comment: Some of these warnings are incorrect, too; os.popen() and fdopen() remain in Python 3. -- ___ Python tracker ___ ___

[issue4662] posix module lacks several DeprecationWarning's

Martin v. Löwis added the comment: I think the policy is that it is ok to add more 3k warnings to 2.7; these are not considered new features (or explicitly exempted, or some such). -- ___ Python tracker __

[issue7716] IPv6 detection, don't assume existence of /usr/xpg4/bin/grep

Sandro Tosi added the comment: Hi, I think the best way to test this patch is to apply the fix and then compile python on a Solaris system (which I don't have): is someone owning a Solaris would run this test? -- nosy: +sandro.tosi ___ Python track

[issue8013] time.asctime segfaults when given a time in the far future

Sandro Tosi added the comment: Hi Ned, thanks for the fast check! I tried to applied the patch (it failed, so it required a bit of manual editing) but when compiling I got: /home/morph/python-dev/py3k/Modules/timemodule.c: In function ‘time_asctime’: /home/morph/python-dev/py3k/Modules/timemo

[issue8013] time.asctime segfaults when given a time in the far future

Changes by Ned Deily : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue8013] time.asctime segfaults when given a time in the far future

Ned Deily added the comment: It's still a problem on OS X at least and is 64-bit related: $ arch -i386 /usr/local/bin/python3.2 -c 'import time;print(time.asctime(time.gmtime(1e12)))' Traceback (most recent call last): File "", line 1, in ValueError: timestamp out of range for platform time

[issue4662] posix module lacks several DeprecationWarning's

Changes by Sandro Tosi : -- versions: +Python 2.7 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue4662] posix module lacks several DeprecationWarning's

Changes by Sandro Tosi : -- versions: -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue4662] posix module lacks several DeprecationWarning's

Sandro Tosi added the comment: The patch no longer applies cleanly to 2.7 head (but it should be trivial to update it). Martin, Benjamin: as this targets 2.7, do you think the patch is acceptable in that branch or it's too late? -- nosy: +sandro.tosi

[issue8278] os.utime doesn't allow a atime (Last Access) which is 27 years in the future.

Sandro Tosi added the comment: Hi Amaury, Martin ack'ed the patch: is there something else you want to do? -- nosy: +sandro.tosi ___ Python tracker ___ __

[issue10242] unittest's assertItemsEqual() method makes too many assumptions about its input

Raymond Hettinger added the comment: The improved output format in 3.2 still needs to be backported to 2.7. -- priority: normal -> low versions: -Python 3.2 ___ Python tracker

[issue10789] Lock.acquire documentation is misleading

Terry J. Reedy added the comment: OK, I will add defaults in the texts and condense them a bit at the same time. Will post patches for review. "Arguments that can't be given as kwargs are presented with brackets." I think this should be stated in the introduction to the Lib manual, along with

[issue8013] time.asctime segfaults when given a time in the far future

Sandro Tosi added the comment: Hi Alexander, can you confirm this bug is MacOs specific? I tried with python2.6 on a Debian sid @64 bit but I can't replicate it. Also, do you see it only on 2.6? if so, I doubt that it will ever be fixed; f.e. on release2.7 branch I have: Python 2.7.1+ (relea

[issue10044] small int optimization

Meador Inge added the comment: > How is the compiler supposed to know whether a and b belong to the same > array when compiling ptr_compare? I agree with Mark, it doesn't need to know. However, many compilers [1,2] support whole program optimization and could in theory figure the address out

[issue10789] Lock.acquire documentation is misleading

Georg Brandl added the comment: No, that's not true. Arguments that can't be given as kwargs are presented with brackets. However, the default value now isn't indicated anywhere; it should be added to the main text. -- ___ Python tracker

[issue10789] Lock.acquire documentation is misleading

Éric Araujo added the comment: I think this commit should be reverted: Arguments with default values no longer use brackets, see for example r73291. More info on #8350. -- nosy: +eric.araujo, georg.brandl ___ Python tracker

[issue8626] TypeError: rsplit() takes no keyword arguments

Éric Araujo added the comment: The description for the function directive is at http://docs.python.org/dev/documenting/markup.html However, I’m not sure whether the doc is accurate, since there was a switch from spam([style]) to spam(style=None) some time ago, for example in r73291. Let’s c

[issue10787] [random.gammavariate] Add the expression of the distribution in a comprehensive form for random.gammavariate

David Kremer added the comment: Yes I agree. Actually the parameters in the python code alpha, beta are corresponding respectively to k, theta in the first equation of [http://en.wikipedia.org/wiki/Gamma_distribution]. -- ___ Python tracker

[issue10130] Create epub format docs and offer them on the download page

Sandro Tosi added the comment: Hi, I've updated the patch, to also mention the 'epub' target in Dco/README.txt but mainly to fix an HTML error in indexcontent.html that prevents the epub to be correctly generated. -- Added file: http://bugs.python.org/file20212/issue10130-v2-py3k.patc

[issue10801] zipfile.ZipFile().extractall() header mismatch for non-ASCII characters

Georg Brandl added the comment: Well, it looks like the filesystem encoding is set to ASCII on these machines. -- ___ Python tracker ___

[issue10801] zipfile.ZipFile().extractall() header mismatch for non-ASCII characters

Eli Bendersky added the comment: Georg, did you figure out the root cause of the problem on that buildbot? Seeing it fails in open(targetpath, "wb"), extracting the file may have failed if the bot had no write permissions to the current directory, but the ascii encoding error is not what I'd

[issue10801] zipfile.ZipFile().extractall() header mismatch for non-ASCII characters

Georg Brandl added the comment: OK, I think r87606 fixed it: it doesn't extract the files, instead calls only open(). -- status: open -> closed ___ Python tracker ___ _

[issue8626] TypeError: rsplit() takes no keyword arguments

Sandro Tosi added the comment: That's interesting: do we have a place where we explain how to read the doc? I mean, a place were we can provide example/explain how we write docs, so f.e.: str.rsplit([sep[, maxsplit]]) is a description for a method that could accept 2 optional arguments, n

[issue444582] Finding programs in PATH, adding shutil.which

Sandro Tosi added the comment: Hi Jan, are you still going to work on this feature? Hi Éric, what are we going to do: include Jan's patch when ready or Trent's `which` tool on google code? Cheers, Sandro -- nosy: +sandro.tosi ___ Python tracker <

[issue10801] zipfile.ZipFile().extractall() header mismatch for non-ASCII characters

Georg Brandl added the comment: OK, looks like there is a problem on some buildbots: http://www.python.org/dev/buildbot/all/builders/AMD64%20Gentoo%20Wide%203.x/builds/863/steps/test/logs/stdio -- status: closed -> open ___ Python tracker

[issue10801] zipfile.ZipFile().extractall() header mismatch for non-ASCII characters

Georg Brandl added the comment: Committed patch and test in r87604. -- nosy: +georg.brandl resolution: -> accepted status: open -> closed ___ Python tracker ___ ___

[issue1674555] sys.path in tests contains system directories

Martin v. Löwis added the comment: I find the solution (running every test in a subprocess) a bit too drastic for the problem. How about a modified approach: run regrtest with -S, and have it create a subprocess for test_site only? -- ___ Python tr