[ python-Bugs-1611131 ] \b in unicode regex gives strange results
Bugs item #1611131, was opened at 2006-12-07 22:44 Message generated for change (Comment added) made by loewis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1611131&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: Regular Expressions Group: Python 2.5 Status: Open Resolution: None Priority: 5 Private: No Submitted By: akaihola (akaihola) Assigned to: Gustavo Niemeyer (niemeyer) Summary: \b in unicode regex gives strange results Initial Comment: The problem: This doesn't give a match: >>> re.match(r'ä\b', 'ä ', re.UNICODE) This works ok and gives a match: >>> re.match(r'.\b', 'ä ', re.UNICODE) Both of these work as well: >>> re.match(r'a\b', 'a ', re.UNICODE) >>> re.match(r'.\b', 'a ', re.UNICODE) Docs say \b is defined as an empty string between \w and \W. These do match accordingly: >>> re.match(r'\w', 'ä', re.UNICODE) >>> re.match(r'\w', 'a', re.UNICODE) >>> re.match(r'\W', ' ', re.UNICODE) So something strange happens in my first example, and I can't help but assume it's a bug. -- >Comment By: Martin v. Löwis (loewis) Date: 2006-12-08 18:18 Message: Logged In: YES user_id=21627 Originator: NO Notice that the re.UNICODE flag is only meaningful if you are using Unicode strings; in the examples you give, you are using byte strings. Please re-test with Unicode strings both as the expression and as the string to match. -- Comment By: akaihola (akaihola) Date: 2006-12-07 23:18 Message: Logged In: YES user_id=1432932 Originator: YES As a work-around I currently use a regex like r'ä(?=\W)'. Seems to work ok. Also, the \b problem doesn't seem to exist in the \W\w case, i.e. at the beginning of words. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1611131&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1576657 ] dict keyerror formatting and tuples
Bugs item #1576657, was opened at 2006-10-13 11:00
Message generated for change (Comment added) made by rhettinger
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1576657&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 Interpreter Core
Group: Python 2.5
Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: M.-A. Lemburg (lemburg)
Assigned to: Georg Brandl (gbrandl)
Summary: dict keyerror formatting and tuples
Initial Comment:
Probably just a minor glitch, but one which caused me
half an hour to track down:
>>> d = {1:'x'}
>>> v = (1,)
>>> d[v]
Traceback (most recent call last):
File "", line 1, in
KeyError: 1
Note the formatting of the error message. It reads '1',
not '(1,)' as you would expect.
The example is constructed. In the code I was
debugging, I didn't know that v was a tuple and thought
it was the integer 1 - so the KeyError itself was
somewhat puzzling.
Only after printing the key I found that the lookup
failed due to a type error.
This happens in Python 2.4 and 2.5.
--
>Comment By: Raymond Hettinger (rhettinger)
Date: 2006-12-08 12:37
Message:
Logged In: YES
user_id=80475
Originator: NO
Added a similar fix to Objects/setobject.c in revision 52964.
--
Comment By: Georg Brandl (gbrandl)
Date: 2006-11-02 11:18
Message:
Logged In: YES
user_id=849994
Patch was committed as rev. 52535/6.
--
Comment By: Georg Brandl (gbrandl)
Date: 2006-10-14 02:16
Message:
Logged In: YES
user_id=849994
This is because a tuple as exception "argument" is
automatically unpacked as the arguments on NormalizeException.
Attaching patch that wraps all KeyErrors from dictionaries
in a tuple. (There may be other objects and exceptions where
this must be handled)
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1576657&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1611753 ] can't pickle NAN's in binary mode
Bugs item #1611753, was opened at 2006-12-08 10:45
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=1611753&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
Private: No
Submitted By: Wayne Christopher (wayne606)
Assigned to: Nobody/Anonymous (nobody)
Summary: can't pickle NAN's in binary mode
Initial Comment:
I think the problem is that pack(">d", float("nan")) does not work. Same for
Inf. This works fine with pickle in ascii mode. I tried this on SuSE 10.0,
x86_64.
Python 2.4.2 (#2, Sep 10 2006, 23:53:27)
[GCC 4.1.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pickle
>>> foo = [1, 2, float("nan")]
>>> foo
[1, 2, nan]
>>> fp = file("/tmp/xxx", "wb")
>>> pickle.dump(foo, fp, -1)
Traceback (most recent call last):
File "", line 1, in ?
File "/home/software/64/lib/python2.4/pickle.py", line 1382, in dump
Pickler(file, protocol, bin).dump(obj)
File "/home/software/64/lib/python2.4/pickle.py", line 231, in dump
self.save(obj)
File "/home/software/64/lib/python2.4/pickle.py", line 293, in save
f(self, obj) # Call unbound method with explicit self
File "/home/software/64/lib/python2.4/pickle.py", line 614, in save_list
self._batch_appends(iter(obj))
File "/home/software/64/lib/python2.4/pickle.py", line 647, in _batch_appends
save(x)
File "/home/software/64/lib/python2.4/pickle.py", line 293, in save
f(self, obj) # Call unbound method with explicit self
File "/home/software/64/lib/python2.4/pickle.py", line 489, in save_float
self.write(BINFLOAT + pack('>d', obj))
SystemError: frexp() result out of range
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1611753&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1611131 ] \b in unicode regex gives strange results
Bugs item #1611131, was opened at 2006-12-07 21:44 Message generated for change (Comment added) made by gbrandl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1611131&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: Regular Expressions Group: Python 2.5 Status: Open Resolution: None Priority: 5 Private: No Submitted By: akaihola (akaihola) Assigned to: Gustavo Niemeyer (niemeyer) Summary: \b in unicode regex gives strange results Initial Comment: The problem: This doesn't give a match: >>> re.match(r'ä\b', 'ä ', re.UNICODE) This works ok and gives a match: >>> re.match(r'.\b', 'ä ', re.UNICODE) Both of these work as well: >>> re.match(r'a\b', 'a ', re.UNICODE) >>> re.match(r'.\b', 'a ', re.UNICODE) Docs say \b is defined as an empty string between \w and \W. These do match accordingly: >>> re.match(r'\w', 'ä', re.UNICODE) >>> re.match(r'\w', 'a', re.UNICODE) >>> re.match(r'\W', ' ', re.UNICODE) So something strange happens in my first example, and I can't help but assume it's a bug. -- >Comment By: Georg Brandl (gbrandl) Date: 2006-12-08 20:51 Message: Logged In: YES user_id=849994 Originator: NO FWIW, the first example works fine for me with and without Unicode strings. -- Comment By: Martin v. Löwis (loewis) Date: 2006-12-08 17:18 Message: Logged In: YES user_id=21627 Originator: NO Notice that the re.UNICODE flag is only meaningful if you are using Unicode strings; in the examples you give, you are using byte strings. Please re-test with Unicode strings both as the expression and as the string to match. -- Comment By: akaihola (akaihola) Date: 2006-12-07 22:18 Message: Logged In: YES user_id=1432932 Originator: YES As a work-around I currently use a regex like r'ä(?=\W)'. Seems to work ok. Also, the \b problem doesn't seem to exist in the \W\w case, i.e. at the beginning of words. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1611131&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1610485 ] GUI for Python 2.3, 2.4, and 2.5 is very sluggish
Bugs item #1610485, was opened at 2006-12-06 18:44 Message generated for change (Comment added) made by g4rlik You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1610485&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: IDLE Group: Python 2.5 Status: Open Resolution: Works For Me Priority: 5 Private: No Submitted By: g4rlik (g4rlik) Assigned to: Kurt B. Kaiser (kbk) Summary: GUI for Python 2.3, 2.4, and 2.5 is very sluggish Initial Comment: The GUI for Python versions 2.3, 2.4, and 2.5 are very sluggish. When I type in them, or simply move them around my desktop, they are very slow. Someone helping me from [EMAIL PROTECTED] was able to guess that the reason the GUI is slow for me is because of the subprocesses running, and he was right. To cope with this problem, I created an idle.txt file, and added this to the first line of it: c:\python25\python c:\python25\Lib\idlelib\idle.py -n After that I saved the extension to .bat and now when I run that file, the Python GUI opens without any subprocesses running and I have no problem. However, I'd still really like to know how I could fix this problem even more. The GUIs for Python version 2.2 and below run fine for me. I am using Windows XP Home Edition Service Pack 2. -- >Comment By: g4rlik (g4rlik) Date: 2006-12-08 16:51 Message: Logged In: YES user_id=1662589 Originator: YES I'd just like to say thanks for looking into the problem. As for now, I can either deal with it or use Python 2.2, it's no problem. -- Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-08 00:13 Message: Logged In: YES user_id=149084 Originator: NO Your system is powerful enough, by an order of magnitude :-) My W2K system is about 400 Mhz. It shows no slowdown with 2.3 - 2.5. If your system is slow only with the subprocess, there must be something about using the socket interface that is problematic. I don't know much about XP Home, but I vaguely recollect hearing about some difficulties with it. You might try upgrading to Win XP Pro, or install Linux. -- Comment By: g4rlik (g4rlik) Date: 2006-12-07 19:14 Message: Logged In: YES user_id=1662589 Originator: YES I ran some programs to get rid of adaware and spyware and then tried to run the GUI for 2.5. I still have the problem. After that I unplugged my router (which has the internal firewall) and attempted to test the GUI's speed again. It was still sluggish. When running the GUI and looking in Task Manager, it uses <1% of my CPU's power. By the way, the specs for my computer are: AMD Athlon XP 2800+ (2.08ghz) 1 gig RAM I don't have an amazing rig, but that should do more than fine for running Python. I don't believe my CPU and RAM are my problems. Oh well, I don't think there is much more looking into this that I can do. I'll either have to live with the sluggishness or run Python 2.2. Thanks. -- Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-07 00:53 Message: Logged In: YES user_id=149084 Originator: NO I have not seen anything like this myself on W2K or WinXP, nor have I heard of something like this before. We switched to the subprocess version of IDLE at 2.3. When printing a mass of text to the Shell window, IDLE is about 30% slower when using the subprocess, but that doesn't sound like what you are reporting. When I move IDLE's windows around there is no perceptible delay, nor can I detect any slowness when typing. (The 30% isn't involved when doing that). I can run i = 1 while True: i +=1 print i and the GUI responds quickly even though the cpu is near 100%. If the solution works for you, fine, but it seems likely to me that there is something misconfigured with your Windows installation or that it is compromised by spyware or otherwise overloaded or having a hardware problem. I'm setting this bug as pending, works for me unless you can come up with something more definitive. What does your Task Manager show for CPU utilization when you are having this problem? It seems that something is hogging your cpu or you have a very slow computer. What's the clock rate and memory size? If you are running an internal firewall, try disconnecting from the net and turn off the firewall temporarily to see if the problem is there. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1610485&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or
[ python-Bugs-1610485 ] GUI for Python 2.3, 2.4, and 2.5 is very sluggish
Bugs item #1610485, was opened at 2006-12-06 18:44 Message generated for change (Comment added) made by kbk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1610485&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: IDLE Group: Python 2.5 >Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: g4rlik (g4rlik) Assigned to: Kurt B. Kaiser (kbk) Summary: GUI for Python 2.3, 2.4, and 2.5 is very sluggish Initial Comment: The GUI for Python versions 2.3, 2.4, and 2.5 are very sluggish. When I type in them, or simply move them around my desktop, they are very slow. Someone helping me from [EMAIL PROTECTED] was able to guess that the reason the GUI is slow for me is because of the subprocesses running, and he was right. To cope with this problem, I created an idle.txt file, and added this to the first line of it: c:\python25\python c:\python25\Lib\idlelib\idle.py -n After that I saved the extension to .bat and now when I run that file, the Python GUI opens without any subprocesses running and I have no problem. However, I'd still really like to know how I could fix this problem even more. The GUIs for Python version 2.2 and below run fine for me. I am using Windows XP Home Edition Service Pack 2. -- >Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-08 17:21 Message: Logged In: YES user_id=149084 Originator: NO OK, I'll close this for now. Feel free to reopen it if you come up with something definitive and/or can find others having the same problem. Can you give me a link to the discussion on [EMAIL PROTECTED] -- Comment By: g4rlik (g4rlik) Date: 2006-12-08 16:51 Message: Logged In: YES user_id=1662589 Originator: YES I'd just like to say thanks for looking into the problem. As for now, I can either deal with it or use Python 2.2, it's no problem. -- Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-08 00:13 Message: Logged In: YES user_id=149084 Originator: NO Your system is powerful enough, by an order of magnitude :-) My W2K system is about 400 Mhz. It shows no slowdown with 2.3 - 2.5. If your system is slow only with the subprocess, there must be something about using the socket interface that is problematic. I don't know much about XP Home, but I vaguely recollect hearing about some difficulties with it. You might try upgrading to Win XP Pro, or install Linux. -- Comment By: g4rlik (g4rlik) Date: 2006-12-07 19:14 Message: Logged In: YES user_id=1662589 Originator: YES I ran some programs to get rid of adaware and spyware and then tried to run the GUI for 2.5. I still have the problem. After that I unplugged my router (which has the internal firewall) and attempted to test the GUI's speed again. It was still sluggish. When running the GUI and looking in Task Manager, it uses <1% of my CPU's power. By the way, the specs for my computer are: AMD Athlon XP 2800+ (2.08ghz) 1 gig RAM I don't have an amazing rig, but that should do more than fine for running Python. I don't believe my CPU and RAM are my problems. Oh well, I don't think there is much more looking into this that I can do. I'll either have to live with the sluggishness or run Python 2.2. Thanks. -- Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-07 00:53 Message: Logged In: YES user_id=149084 Originator: NO I have not seen anything like this myself on W2K or WinXP, nor have I heard of something like this before. We switched to the subprocess version of IDLE at 2.3. When printing a mass of text to the Shell window, IDLE is about 30% slower when using the subprocess, but that doesn't sound like what you are reporting. When I move IDLE's windows around there is no perceptible delay, nor can I detect any slowness when typing. (The 30% isn't involved when doing that). I can run i = 1 while True: i +=1 print i and the GUI responds quickly even though the cpu is near 100%. If the solution works for you, fine, but it seems likely to me that there is something misconfigured with your Windows installation or that it is compromised by spyware or otherwise overloaded or having a hardware problem. I'm setting this bug as pending, works for me unless you can come up with something more definitive. What does your Task Manager show for CPU utilization when you are having this problem? It seems that something is hogging your cpu or you have a very slow computer. What's the clock rate and memory size? If you are running an internal firewall, try discon
[ python-Bugs-1611944 ] sndhdr.what() does not recognize wav file
Bugs item #1611944, was opened at 2006-12-09 03:37 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=1611944&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.5 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Floris van Manen (klankschap) Assigned to: Nobody/Anonymous (nobody) Summary: sndhdr.what() does not recognize wav file Initial Comment: using 2.5 on osx 10.4 the sndhdr.what() function fails to recognize some wav headers. however these wav files are recognized correctly by other 'standard' applications like quicktime and itunes. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1611944&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1610485 ] GUI for Python 2.3, 2.4, and 2.5 is very sluggish
Bugs item #1610485, was opened at 2006-12-06 18:44 Message generated for change (Comment added) made by g4rlik You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1610485&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: IDLE Group: Python 2.5 Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: g4rlik (g4rlik) Assigned to: Kurt B. Kaiser (kbk) Summary: GUI for Python 2.3, 2.4, and 2.5 is very sluggish Initial Comment: The GUI for Python versions 2.3, 2.4, and 2.5 are very sluggish. When I type in them, or simply move them around my desktop, they are very slow. Someone helping me from [EMAIL PROTECTED] was able to guess that the reason the GUI is slow for me is because of the subprocesses running, and he was right. To cope with this problem, I created an idle.txt file, and added this to the first line of it: c:\python25\python c:\python25\Lib\idlelib\idle.py -n After that I saved the extension to .bat and now when I run that file, the Python GUI opens without any subprocesses running and I have no problem. However, I'd still really like to know how I could fix this problem even more. The GUIs for Python version 2.2 and below run fine for me. I am using Windows XP Home Edition Service Pack 2. -- >Comment By: g4rlik (g4rlik) Date: 2006-12-08 21:54 Message: Logged In: YES user_id=1662589 Originator: YES I'm not exactly sure how I'd give you a link to the discussion on [EMAIL PROTECTED] I was talking via e-mail and I'm not sure how to link that. Would you want me to copy and paste it? -- Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-08 17:21 Message: Logged In: YES user_id=149084 Originator: NO OK, I'll close this for now. Feel free to reopen it if you come up with something definitive and/or can find others having the same problem. Can you give me a link to the discussion on [EMAIL PROTECTED] -- Comment By: g4rlik (g4rlik) Date: 2006-12-08 16:51 Message: Logged In: YES user_id=1662589 Originator: YES I'd just like to say thanks for looking into the problem. As for now, I can either deal with it or use Python 2.2, it's no problem. -- Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-08 00:13 Message: Logged In: YES user_id=149084 Originator: NO Your system is powerful enough, by an order of magnitude :-) My W2K system is about 400 Mhz. It shows no slowdown with 2.3 - 2.5. If your system is slow only with the subprocess, there must be something about using the socket interface that is problematic. I don't know much about XP Home, but I vaguely recollect hearing about some difficulties with it. You might try upgrading to Win XP Pro, or install Linux. -- Comment By: g4rlik (g4rlik) Date: 2006-12-07 19:14 Message: Logged In: YES user_id=1662589 Originator: YES I ran some programs to get rid of adaware and spyware and then tried to run the GUI for 2.5. I still have the problem. After that I unplugged my router (which has the internal firewall) and attempted to test the GUI's speed again. It was still sluggish. When running the GUI and looking in Task Manager, it uses <1% of my CPU's power. By the way, the specs for my computer are: AMD Athlon XP 2800+ (2.08ghz) 1 gig RAM I don't have an amazing rig, but that should do more than fine for running Python. I don't believe my CPU and RAM are my problems. Oh well, I don't think there is much more looking into this that I can do. I'll either have to live with the sluggishness or run Python 2.2. Thanks. -- Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-07 00:53 Message: Logged In: YES user_id=149084 Originator: NO I have not seen anything like this myself on W2K or WinXP, nor have I heard of something like this before. We switched to the subprocess version of IDLE at 2.3. When printing a mass of text to the Shell window, IDLE is about 30% slower when using the subprocess, but that doesn't sound like what you are reporting. When I move IDLE's windows around there is no perceptible delay, nor can I detect any slowness when typing. (The 30% isn't involved when doing that). I can run i = 1 while True: i +=1 print i and the GUI responds quickly even though the cpu is near 100%. If the solution works for you, fine, but it seems likely to me that there is something misconfigured with your Windows installation or that it is compromised by spyware or otherwise overloaded or having a hardwar
[ python-Bugs-1610485 ] GUI for Python 2.3, 2.4, and 2.5 is very sluggish
Bugs item #1610485, was opened at 2006-12-06 18:44 Message generated for change (Comment added) made by kbk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1610485&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: IDLE Group: Python 2.5 Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: g4rlik (g4rlik) Assigned to: Kurt B. Kaiser (kbk) Summary: GUI for Python 2.3, 2.4, and 2.5 is very sluggish Initial Comment: The GUI for Python versions 2.3, 2.4, and 2.5 are very sluggish. When I type in them, or simply move them around my desktop, they are very slow. Someone helping me from [EMAIL PROTECTED] was able to guess that the reason the GUI is slow for me is because of the subprocesses running, and he was right. To cope with this problem, I created an idle.txt file, and added this to the first line of it: c:\python25\python c:\python25\Lib\idlelib\idle.py -n After that I saved the extension to .bat and now when I run that file, the Python GUI opens without any subprocesses running and I have no problem. However, I'd still really like to know how I could fix this problem even more. The GUIs for Python version 2.2 and below run fine for me. I am using Windows XP Home Edition Service Pack 2. -- >Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-08 23:42 Message: Logged In: YES user_id=149084 Originator: NO Yes, please do. -- Comment By: g4rlik (g4rlik) Date: 2006-12-08 21:54 Message: Logged In: YES user_id=1662589 Originator: YES I'm not exactly sure how I'd give you a link to the discussion on [EMAIL PROTECTED] I was talking via e-mail and I'm not sure how to link that. Would you want me to copy and paste it? -- Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-08 17:21 Message: Logged In: YES user_id=149084 Originator: NO OK, I'll close this for now. Feel free to reopen it if you come up with something definitive and/or can find others having the same problem. Can you give me a link to the discussion on [EMAIL PROTECTED] -- Comment By: g4rlik (g4rlik) Date: 2006-12-08 16:51 Message: Logged In: YES user_id=1662589 Originator: YES I'd just like to say thanks for looking into the problem. As for now, I can either deal with it or use Python 2.2, it's no problem. -- Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-08 00:13 Message: Logged In: YES user_id=149084 Originator: NO Your system is powerful enough, by an order of magnitude :-) My W2K system is about 400 Mhz. It shows no slowdown with 2.3 - 2.5. If your system is slow only with the subprocess, there must be something about using the socket interface that is problematic. I don't know much about XP Home, but I vaguely recollect hearing about some difficulties with it. You might try upgrading to Win XP Pro, or install Linux. -- Comment By: g4rlik (g4rlik) Date: 2006-12-07 19:14 Message: Logged In: YES user_id=1662589 Originator: YES I ran some programs to get rid of adaware and spyware and then tried to run the GUI for 2.5. I still have the problem. After that I unplugged my router (which has the internal firewall) and attempted to test the GUI's speed again. It was still sluggish. When running the GUI and looking in Task Manager, it uses <1% of my CPU's power. By the way, the specs for my computer are: AMD Athlon XP 2800+ (2.08ghz) 1 gig RAM I don't have an amazing rig, but that should do more than fine for running Python. I don't believe my CPU and RAM are my problems. Oh well, I don't think there is much more looking into this that I can do. I'll either have to live with the sluggishness or run Python 2.2. Thanks. -- Comment By: Kurt B. Kaiser (kbk) Date: 2006-12-07 00:53 Message: Logged In: YES user_id=149084 Originator: NO I have not seen anything like this myself on W2K or WinXP, nor have I heard of something like this before. We switched to the subprocess version of IDLE at 2.3. When printing a mass of text to the Shell window, IDLE is about 30% slower when using the subprocess, but that doesn't sound like what you are reporting. When I move IDLE's windows around there is no perceptible delay, nor can I detect any slowness when typing. (The 30% isn't involved when doing that). I can run i = 1 while True: i +=1 print i and the GUI responds quickly even though the cpu is near 100%. If the soluti
[ python-Bugs-1612012 ] builtin compile() doc needs PyCF_DONT_IMPLY_DEDENT
Bugs item #1612012, was opened at 2006-12-09 16:45 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=1612012&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Anthony Baxter (anthonybaxter) Assigned to: Nobody/Anonymous (nobody) Summary: builtin compile() doc needs PyCF_DONT_IMPLY_DEDENT Initial Comment: http://docs.python.org/lib/built-in-funcs.html doesn't mention the flag PyCF_DONT_IMPLY_DEDENT, as used by codeop.py in the stdlib. (I note that codeop.py has that flag as a literal, copied out of pythonrun.h - it should probably be exposed in some way). -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1612012&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
