[issue4081] Error copying directory to _static in Sphinx
Tim Delaney [EMAIL PROTECTED] added the comment: Confirmed fixed in 0.43 - this issue can be closed. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4081 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4081] Error copying directory to _static in Sphinx
New submission from Tim Delaney [EMAIL PROTECTED]: If there is a directory to be copied to _static, Sphinx first attempts to delete any directory by the same name in the _static directory. See attached sphinx_static_exc.txt for the exception. The simplest fix is to change the call (line 595, Sphinx 0.4.2) to:: shutil.rmtree(targetname) to:: shutil.rmtree(targetname, ignore_errors=True) It would also be preferable if instead of blindly doing rmtree/copytree, only updated files be copied to _static. -- assignee: georg.brandl components: Documentation tools (Sphinx) files: sphinx_static_exc.txt messages: 74551 nosy: georg.brandl, tcdelaney severity: normal status: open title: Error copying directory to _static in Sphinx type: crash Added file: http://bugs.python.org/file11752/sphinx_static_exc.txt ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4081 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4081] Error copying directory to _static in Sphinx
Tim Delaney [EMAIL PROTECTED] added the comment: Oops - didn't complete my thought. The issue is that if the directory does not already exist, the attached exception is raised. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4081 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1733134] sqlite3.dll cannot be relocated
Tim Delaney added the comment: I've got no further details on this bug - I've never encountered it myself. _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1733134 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1196] int() documentation does not specify default radix
New submission from Tim Delaney: The int() documentation (section 2.1) does not specify the default radix used. Alternatively, it does not specify the default behaviour for string parsing. Experimentally, it's parsing with a default radix of 10 - I recall in an earlier version of Python it parsed with a default radix of zero (i.e. dependent on the string contents). I would suggest the following text: int( [x[, radix]]) Convert a string or number to a plain integer. If the argument is a string, it must contain a possibly signed decimal number representable as a Python integer, possibly embedded in whitespace. The radix parameter gives the base for the conversion and may be any integer in the range [2, 36], or zero. If radix is zero, the proper radix is guessed based on the contents of string; the interpretation is the same as for integer literals. If radix is specified and x is not a string, TypeError is raised. If radix is not specified, and x is a string, the interpretation is as if a radix of 10 was specified. Otherwise, the argument may be a plain or long integer or a floating point number. Conversion of floating point numbers to integers truncates (towards zero). If the argument is outside the integer range a long object will be returned instead. If no arguments are given, returns 0. -- components: Documentation messages: 56110 nosy: tcdelaney severity: normal status: open title: int() documentation does not specify default radix versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1196 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
