[ python-Bugs-1412227 ] minor doc issues in os
Bugs item #1412227, was opened at 2006-01-22 20:04 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1412227&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: Not a Bug Status: Open Resolution: None Priority: 5 Submitted By: tiissa (tiissa) Assigned to: Nobody/Anonymous (nobody) Summary: minor doc issues in os Initial Comment: Section 6.1.4 in libos.tex, in the description of the stat function, there is a new paragraph on FreeBSD with an incomplete parenthesis: ..."may be available (but may be only filled out of root tries to use them:" I guess it should read "(but may be only filled out if root tries to use them):" (but I may be wrong). Also, in the walk function, there is a typo : one "dirnames" should be "dirpath" instead (when describing the effect of a modification of dirnames in a bottom-up walk). In this same walk function, os.error is used although OSError is used everywhere else (to my incomplete knowledge). Is there a reason? I join a patch with these corrections and some small LaTeX macro changes in stat_float_times. Thank you. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1412227&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1412227 ] minor doc issues in os
Bugs item #1412227, was opened at 2006-01-22 20:04 Message generated for change (Settings changed) made by tiissa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1412227&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: Not a Bug Status: Open Resolution: None >Priority: 1 Submitted By: tiissa (tiissa) Assigned to: Nobody/Anonymous (nobody) Summary: minor doc issues in os Initial Comment: Section 6.1.4 in libos.tex, in the description of the stat function, there is a new paragraph on FreeBSD with an incomplete parenthesis: ..."may be available (but may be only filled out of root tries to use them:" I guess it should read "(but may be only filled out if root tries to use them):" (but I may be wrong). Also, in the walk function, there is a typo : one "dirnames" should be "dirpath" instead (when describing the effect of a modification of dirnames in a bottom-up walk). In this same walk function, os.error is used although OSError is used everywhere else (to my incomplete knowledge). Is there a reason? I join a patch with these corrections and some small LaTeX macro changes in stat_float_times. Thank you. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1412227&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1412227 ] minor doc issues in os
Bugs item #1412227, was opened at 2006-01-22 20:04 Message generated for change (Comment added) made by birkenfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1412227&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: Not a Bug >Status: Closed >Resolution: Fixed Priority: 1 Submitted By: tiissa (tiissa) Assigned to: Nobody/Anonymous (nobody) Summary: minor doc issues in os Initial Comment: Section 6.1.4 in libos.tex, in the description of the stat function, there is a new paragraph on FreeBSD with an incomplete parenthesis: ..."may be available (but may be only filled out of root tries to use them:" I guess it should read "(but may be only filled out if root tries to use them):" (but I may be wrong). Also, in the walk function, there is a typo : one "dirnames" should be "dirpath" instead (when describing the effect of a modification of dirnames in a bottom-up walk). In this same walk function, os.error is used although OSError is used everywhere else (to my incomplete knowledge). Is there a reason? I join a patch with these corrections and some small LaTeX macro changes in stat_float_times. Thank you. -- >Comment By: Georg Brandl (birkenfeld) Date: 2006-01-22 20:35 Message: Logged In: YES user_id=1188172 Thanks for pointing those out! Committed revisions 42142, 42143 (2.4). -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1412227&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1412580 ] locale.format gives wrong exception on some erroneous input
Bugs item #1412580, was opened at 2006-01-23 07:46
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1412580&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Diggins (tdiggins)
Assigned to: Nobody/Anonymous (nobody)
Summary: locale.format gives wrong exception on some erroneous input
Initial Comment:
using '2.4.2 (#67, Sep 28 2005, 12:41:11) [MSC v.1310
32 bit (Intel)]' on WinXpPro SP2
locale.format(formatString, val, grouping) when passed
a formatString of the wrong type, ought to raise a
TypeError (as some erroneous input does)
Example: locale.format(2.3, 2.3) passes through
AttributeError ("float has no attribute 'split'").
I thought perhaps the body of the method should be
wrapped in a try:except block, and if any error is
caught, then the arguments should be rigorously tested
for type and lucid exceptions raised. See attachment
for suggestion (with tests).
I'm not clear whether if the format string is erroneous
(bad syntax, or has too many/no %-s, the raised error
should be ValueError (contractually correct) or
conceivably whatever StringInterpolation raises
(parallelism). I've put tests for both in - currently
ValueError wins.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1412580&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
