[ python-Feature Requests-1122532 ] Line Numbers
Feature Requests item #1122532, was opened at 2005-02-14 17:28 Message generated for change (Comment added) made by friedrich You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1122532&group_id=5470 Category: IDLE Group: None Status: Open Resolution: None Priority: 4 Submitted By: Egon Frerich (friedrich) Assigned to: Kurt B. Kaiser (kbk) Summary: Line Numbers Initial Comment: The presentation of line numbers would be helpfull. -- >Comment By: Egon Frerich (friedrich) Date: 2005-02-20 10:12 Message: Logged In: YES user_id=37594 Yes, and you know where the cursor is. And there is the Edit-menu item to go to a line number. Helpful means: sometimes you get a python error with the line number. In a GUI you often work with the mouse and you don't want to enter with the keyboard. So you scroll the edit window with the mouse. If there were the line number at the left border you find the line number very quickly and only with the mouse. How I said: helpfull. -- Comment By: Kurt B. Kaiser (kbk) Date: 2005-02-20 01:59 Message: Logged In: YES user_id=149084 Helpful in what way? What are you trying to accomplish? There is a line number indicator on the lower right of each IDLE edit window. -- Comment By: Egon Frerich (friedrich) Date: 2005-02-17 11:18 Message: Logged In: YES user_id=37594 and I should have added: line numbers on the left side of edit sreens, not in the Shell screen -- Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-17 01:25 Message: Logged In: YES user_id=80475 Sorry, I saw the IDLE category sending. -- Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-17 01:24 Message: Logged In: YES user_id=80475 In the editor or someplace else? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1122532&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Feature Requests-1144057 ] future warning in commets
Feature Requests item #1144057, was opened at 2005-02-18 16:10 Message generated for change (Settings changed) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1144057&group_id=5470 >Category: Parser/Compiler >Group: None Status: Open Resolution: None Priority: 5 Submitted By: Grzegorz Makarewicz (makaron) Assigned to: Nobody/Anonymous (nobody) Summary: future warning in commets Initial Comment: Python uses '#' as start of comment, generally these lines can (should) be ignored by python compiler but .. deprecation warnings are issued when comment contains non ascii letters - ord(ch) not in range 0-127 can we disable it in this situation ? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1144057&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1124692 ] Math mode not well handled in \documentclass{howto}
Bugs item #1124692, was opened at 2005-02-17 08:08
Message generated for change (Settings changed) made by rhettinger
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1124692&group_id=5470
Category: Documentation
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniele Varrazzo (dvarrazzo)
>Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: Math mode not well handled in \documentclass{howto}
Initial Comment:
LaTeX loses its Math Magic (tm) when using
\documentclass{howto}: underscore operator in math
enviroment doesn't produce subscripts.
This documents shows some oddities:
\documentclass{howto}
\begin{document}
Water is $H_2O$, and subscript is missing from...
\[ V_{0,r} \]
Superscripts are instead fine, as $e^{\pi i} + 1 = 0$
shows.
Also this is completely different from what obtained by
\textbackslash documentclass\{article\}.
\[ \sum_{k=0}^\infty \int_0^k f(x) dx \]
\end{document}
The bug is removed by commenting out lines 541--549 in
python.sty, but i don't know how to *fix* them... (not a
TeXpert)
Using Python 2.3.5, Windows 2000, LaTeX2e (e-TeX
3.141592-2.2, MikTex 2.4 implementation)
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1124692&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Feature Requests-1123660 ] add SHA256/384/512 to lib
Feature Requests item #1123660, was opened at 2005-02-15 23:14 Message generated for change (Comment added) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1123660&group_id=5470 >Category: Python Library >Group: None Status: Open Resolution: None Priority: 5 Submitted By: paul rubin (phr) Assigned to: Nobody/Anonymous (nobody) Summary: add SHA256/384/512 to lib Initial Comment: According to http://www.schneier.com/blog/archives/2005/02/sha1_broken.html some Chinese researchers have just announced a break against SHA1. These are the same guys who broke MD5 a few months ago and the SHA1 break, while not exactly expected, is also not really shocking at this point. The break allows finding a free collision in the full SHA1 in O(2**69) operations, still an awful lot in practice. So nobody should panic. But it means that new applications probably want to use SHA256, SHA384, or SHA512, which were standardized by NIST at the same time AES was standardized, as successors to SHA1. The hash lengths are 256, 384, or 512 bits respectively, and correspond to 2x the AES key lengths of 128, 192, or 384 bits. Their design is strengthened from SHA1 to resist attacks like this. On the other hand, they are slower than SHA1. Anyway, there are various free implementations of the algorithms around (libtomcrypt.org has some public domain versions) so it should be straightforward enough to transplant the Python C API wrapper from sha.c to it. I think it's reasonable to put these all into the existing sha module, rather than make a new module. They could be called by adding an optional arg to sha.new: x = sha.new(data, 256).digest() would find the sha256 digest, etc. Note that sha512 and sha384 are the same algorithm, with different initial parameters and with 128 bits discarded for sha384. -- >Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-20 05:52 Message: Logged In: YES user_id=80475 "Break" is a bit of an over-statement. -- Comment By: Terry J. Reedy (tjreedy) Date: 2005-02-17 12:45 Message: Logged In: YES user_id=593130 Ok, next time You might want to look at https://sourceforge.net/tracker/index.php? func=detail&aid=1121611&group_id=5470&atid=305470 -- Comment By: paul rubin (phr) Date: 2005-02-17 11:55 Message: Logged In: YES user_id=72053 Well, I don't see an obvious way to reclassify this item. If someone knows how to do it, please go ahead. I sent an email to the lawyer and haven't gotten a response yet. -- Comment By: Terry J. Reedy (tjreedy) Date: 2005-02-17 11:14 Message: Logged In: YES user_id=593130 Addition to the previous: current does not necessarily mean final. I am not a party to any ongoing non-public discussion of these issues. Over and out. -- Comment By: Terry J. Reedy (tjreedy) Date: 2005-02-17 00:25 Message: Logged In: YES user_id=593130 Here is the top of this page: Project: Bugs: Trackers and here is the beginning of the email sent to me: Bugs item #1123660, was opened at 2005-02-16 04:14 I found the explanation: on https://sourceforge.net/tracker/?group_id=5470 you need to click RFE instead of Bugs on this line: Summary | Admin | Home Page | Tracker | Bugs | Patches | RFE | When you click Bugs, Feature Request shows up under Group because it was put there before there was a separate RFE list and now, I remember, it cannot be removed. (SF 'feature') But it would be if it could be. --- Yes, that is the lawyer and article. Yes, I noticed the discrepancy 'PD not real' and current PEP PD policy, but refrained from saying anything yet. I have no more to do with those and other docs than you do. Contributor agreements: your link is to a 3 1/2 year old draft, badly misleading, but first hit on 'contributor' search. I have suggested its removal. Current, I believe, is http://www.python.org/psf/contrib which links to http://www.python.org/moin/PythonSoftwareFoundationLicen seFaq and http://www.python.org/psf/contrib-form.html -- Comment By: paul rubin (phr) Date: 2005-02-16 22:33 Message: Logged In: YES user_id=72053 I couldn't find the "Contributions" section of Python.org; got a url? I did find PEP 241 says public domain is a legitimate choice of license, and also the PSF patch submission agreement near the bottom of http://www.python.org/psf/psf-contributor-agreement.html suggests releasing the patch to the PD (but only if the contributor wrote the entire patch, which wouldn't apply to wrapping some existing public domain work). Also a lot
[ python-Feature Requests-1124503 ] IDLE line wrapping
Feature Requests item #1124503, was opened at 2005-02-16 23:56 Message generated for change (Comment added) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1124503&group_id=5470 >Category: IDLE >Group: None Status: Open Resolution: None Priority: 4 Submitted By: Chris Rebert (rebertc) >Assigned to: Kurt B. Kaiser (kbk) Summary: IDLE line wrapping Initial Comment: As IDLE is the 'official' python editor and PEP 8 (Style Guide PEP) suggests that coders wrap lines at 79 characters, I propose that IDLE should assist this practice by highlighting lines or parts of lines longer than 79 chacacters, or something similar. It is suggested that this be a pref toggleable in the "Configure IDLE" window and be turned on by default to encourage good coding practices. -- >Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-20 05:53 Message: Logged In: YES user_id=80475 I would find this to be an annoyance. Passing to Kurt for pronouncement. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1124503&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1121416 ] zip incorrectly and incompletely documented
Bugs item #1121416, was opened at 2005-02-12 12:18
Message generated for change (Settings changed) made by rhettinger
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1121416&group_id=5470
Category: Documentation
Group: None
Status: Open
Resolution: None
>Priority: 3
Submitted By: Alan (aisaac0)
Assigned to: Raymond Hettinger (rhettinger)
Summary: zip incorrectly and incompletely documented
Initial Comment:
See the zip documentation:
http://www.python.org/dev/doc/devel/lib/built-in-funcs.html
i. documentation refers to sequences not to iterables
ii. The other problem is easier to explain by example.
Let it=iter([1,2,3,4]).
What is the result of zip(*[it]*2)?
The current answer is: [(1,2),(3,4)],
but it is impossible to determine this from the docs,
which would allow [(1,3),(2,4)] instead (or indeed
other possibilities).
The example expresses the solution to an actual need,
so the behavior should be documented or warned against,
I believe.
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2005-02-16 20:10
Message:
Logged In: YES
user_id=80475
The first sentence becomes even less clear with the "in the
same order" wording.
The note about truncating to the shortest sequence length is
essential and should not have been dropped.
The py2.4 change note is in a standard form
(\versionchanged{} following the explanation of current
behavior) and should not have been altered.
The part that addresses the OP's concern is too specific to
the his one example and is unclear unless you know about
that example. The wording is discomforting, doesn't add new
information, and is somewhat not obvious in its meaning.
I suggest simply changing "sequence" to "iterable".
There is no sense in stating that the order of combination
is undefined. It doesn't help with the OP's original desire
to be able to predict the outcome of the example. However,
it does have the negative effect of making a person question
whether they've understood the preceding description of what
actually zip() does do.
zip() is about lockstep iteration and the docs should serve
those users as straight-forwardly as possible. The OP's
issue on the other hand only comes up when trying funky
iterator magic -- adding a sentence about undefined ordering
doesn't help one bit.
There is a lesson in all this. These tools were borrowed
from the world of functional programming which is all about
programming that is free of side-effects. The OP's problem
should be left as a code smell indicating a misuse of
functionals.
--
Comment By: Terry J. Reedy (tjreedy)
Date: 2005-02-16 19:03
Message:
Logged In: YES
user_id=593130
I agree that the zip doc needs improvement. Confusion will
continue until it is. Here is my suggested rewrite:
---
zip([iterable1, ...])
Return a list of tuples, where the i-th tuple contains the i-th
element from each input in the same order as the inputs.
With no arguments, return an empty list (before 2.4, a
TypeError was raised instead.) With a single input, return a
list of 1-tuples. With multiple inputs, the output length is
that of the shorted input. When multiple input lengths are
equal, zip(i1, ...) is similar to map(None, i1, ...), but there is
no padding when otherwise. The result of zipping a volatile
iterable with itself is undefined. New in 2.0.
---
There you have it. More information is about 15% fewer
words. The reduction came from greatly condensing the
overwordy sentence about obsolete behavior into a
parenthetical comment. For comparison, here is the current
version.
---
zip( [seq1, ...])
This function returns a list of tuples, where the i-th tuple
contains the i-th element from each of the argument
sequences. The returned list is truncated in length to the
length of the shortest argument sequence. When there are
multiple argument sequences which are all of the same
length, zip() is similar to map() with an initial argument of
None. With a single sequence argument, it returns a list of 1-
tuples. With no arguments, it returns an empty list. New in
version 2.0.
Changed in version 2.4: Formerly, zip() required at least one
argument and zip() raised a TypeError instead of returning
an empty list..
--
Comment By: Nick Coghlan (ncoghlan)
Date: 2005-02-12 21:25
Message:
Logged In: YES
user_id=1038590
The generator in the previous comment was incorrect (tuple
swallows the StopIteration, so it never terminates). Try
this instead:
def partition(iterable, part_len):
itr = iter(iterable)
while 1:
item = tuple(islice(it
[ python-Feature Requests-1122532 ] Line Numbers
Feature Requests item #1122532, was opened at 2005-02-14 12:28 Message generated for change (Comment added) made by kbk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1122532&group_id=5470 Category: IDLE Group: None Status: Open Resolution: None Priority: 4 Submitted By: Egon Frerich (friedrich) Assigned to: Kurt B. Kaiser (kbk) Summary: Line Numbers Initial Comment: The presentation of line numbers would be helpfull. -- >Comment By: Kurt B. Kaiser (kbk) Date: 2005-02-20 10:54 Message: Logged In: YES user_id=149084 If you right click on the line number in the traceback you will have the option of viewing the associated source code. -- Comment By: Egon Frerich (friedrich) Date: 2005-02-20 05:12 Message: Logged In: YES user_id=37594 Yes, and you know where the cursor is. And there is the Edit-menu item to go to a line number. Helpful means: sometimes you get a python error with the line number. In a GUI you often work with the mouse and you don't want to enter with the keyboard. So you scroll the edit window with the mouse. If there were the line number at the left border you find the line number very quickly and only with the mouse. How I said: helpfull. -- Comment By: Kurt B. Kaiser (kbk) Date: 2005-02-19 20:59 Message: Logged In: YES user_id=149084 Helpful in what way? What are you trying to accomplish? There is a line number indicator on the lower right of each IDLE edit window. -- Comment By: Egon Frerich (friedrich) Date: 2005-02-17 06:18 Message: Logged In: YES user_id=37594 and I should have added: line numbers on the left side of edit sreens, not in the Shell screen -- Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-16 20:25 Message: Logged In: YES user_id=80475 Sorry, I saw the IDLE category sending. -- Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-16 20:24 Message: Logged In: YES user_id=80475 In the editor or someplace else? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1122532&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Feature Requests-1124503 ] IDLE line wrapping
Feature Requests item #1124503, was opened at 2005-02-16 23:56 Message generated for change (Comment added) made by kbk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1124503&group_id=5470 Category: IDLE Group: None >Status: Closed >Resolution: Rejected Priority: 4 Submitted By: Chris Rebert (rebertc) Assigned to: Kurt B. Kaiser (kbk) Summary: IDLE line wrapping Initial Comment: As IDLE is the 'official' python editor and PEP 8 (Style Guide PEP) suggests that coders wrap lines at 79 characters, I propose that IDLE should assist this practice by highlighting lines or parts of lines longer than 79 chacacters, or something similar. It is suggested that this be a pref toggleable in the "Configure IDLE" window and be turned on by default to encourage good coding practices. -- >Comment By: Kurt B. Kaiser (kbk) Date: 2005-02-20 11:00 Message: Logged In: YES user_id=149084 I'd agree with Raymond. Three things have been done to help with this: first, the default window width is set at 80 char. Second, there is a column number indicator in the lower right, it's easy to keep an eye on it when you're typing a long line. Finally, there is a paragraph formatting feature which will re-wrap comments and doc strings to a configurable width. Now if Sourceforge could just do something clever to fix the farging line wrap in these comment windows -- Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-20 05:53 Message: Logged In: YES user_id=80475 I would find this to be an annoyance. Passing to Kurt for pronouncement. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1124503&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Feature Requests-1122532 ] Line Numbers
Feature Requests item #1122532, was opened at 2005-02-14 17:28 Message generated for change (Comment added) made by friedrich You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1122532&group_id=5470 Category: IDLE Group: None Status: Open Resolution: None Priority: 4 Submitted By: Egon Frerich (friedrich) Assigned to: Kurt B. Kaiser (kbk) Summary: Line Numbers Initial Comment: The presentation of line numbers would be helpfull. -- >Comment By: Egon Frerich (friedrich) Date: 2005-02-20 20:01 Message: Logged In: YES user_id=37594 Thank you -- Comment By: Kurt B. Kaiser (kbk) Date: 2005-02-20 15:54 Message: Logged In: YES user_id=149084 If you right click on the line number in the traceback you will have the option of viewing the associated source code. -- Comment By: Egon Frerich (friedrich) Date: 2005-02-20 10:12 Message: Logged In: YES user_id=37594 Yes, and you know where the cursor is. And there is the Edit-menu item to go to a line number. Helpful means: sometimes you get a python error with the line number. In a GUI you often work with the mouse and you don't want to enter with the keyboard. So you scroll the edit window with the mouse. If there were the line number at the left border you find the line number very quickly and only with the mouse. How I said: helpfull. -- Comment By: Kurt B. Kaiser (kbk) Date: 2005-02-20 01:59 Message: Logged In: YES user_id=149084 Helpful in what way? What are you trying to accomplish? There is a line number indicator on the lower right of each IDLE edit window. -- Comment By: Egon Frerich (friedrich) Date: 2005-02-17 11:18 Message: Logged In: YES user_id=37594 and I should have added: line numbers on the left side of edit sreens, not in the Shell screen -- Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-17 01:25 Message: Logged In: YES user_id=80475 Sorry, I saw the IDLE category sending. -- Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-17 01:24 Message: Logged In: YES user_id=80475 In the editor or someplace else? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1122532&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Feature Requests-1122532 ] Line Numbers
Feature Requests item #1122532, was opened at 2005-02-14 12:28 Message generated for change (Settings changed) made by kbk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1122532&group_id=5470 Category: IDLE Group: None >Status: Closed >Resolution: Rejected Priority: 4 Submitted By: Egon Frerich (friedrich) Assigned to: Kurt B. Kaiser (kbk) Summary: Line Numbers Initial Comment: The presentation of line numbers would be helpfull. -- Comment By: Egon Frerich (friedrich) Date: 2005-02-20 15:01 Message: Logged In: YES user_id=37594 Thank you -- Comment By: Kurt B. Kaiser (kbk) Date: 2005-02-20 10:54 Message: Logged In: YES user_id=149084 If you right click on the line number in the traceback you will have the option of viewing the associated source code. -- Comment By: Egon Frerich (friedrich) Date: 2005-02-20 05:12 Message: Logged In: YES user_id=37594 Yes, and you know where the cursor is. And there is the Edit-menu item to go to a line number. Helpful means: sometimes you get a python error with the line number. In a GUI you often work with the mouse and you don't want to enter with the keyboard. So you scroll the edit window with the mouse. If there were the line number at the left border you find the line number very quickly and only with the mouse. How I said: helpfull. -- Comment By: Kurt B. Kaiser (kbk) Date: 2005-02-19 20:59 Message: Logged In: YES user_id=149084 Helpful in what way? What are you trying to accomplish? There is a line number indicator on the lower right of each IDLE edit window. -- Comment By: Egon Frerich (friedrich) Date: 2005-02-17 06:18 Message: Logged In: YES user_id=37594 and I should have added: line numbers on the left side of edit sreens, not in the Shell screen -- Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-16 20:25 Message: Logged In: YES user_id=80475 Sorry, I saw the IDLE category sending. -- Comment By: Raymond Hettinger (rhettinger) Date: 2005-02-16 20:24 Message: Logged In: YES user_id=80475 In the editor or someplace else? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1122532&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
