[ python-Bugs-1145950 ] Strange behaviour concerning variable names
Bugs item #1145950, was opened at 2005-02-22 02:47 Message generated for change (Comment added) made by mwh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1145950&group_id=5470 Category: Parser/Compiler >Group: Not a Bug >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Felix Nawothnig (flexo_) Assigned to: Nobody/Anonymous (nobody) Summary: Strange behaviour concerning variable names Initial Comment: For some reason python coders seem to be unaware of the fact that Python allows variable names to be longer than one char - let's have a look at a function from BitTorrent for example: def decode_list(x, f): r, f = [], f+1 while x[f] != 'e': v, f = decode_func[x[f]](x, f) r.append(v) return (r, f + 1) I'm not sure about the reasons for this behaviour yet but I suspect serious brain-damage caused by indentation-based structuring. A possible workaround: switching to a sane language like Ruby. -- >Comment By: Michael Hudson (mwh) Date: 2005-02-22 10:16 Message: Logged In: YES user_id=6656 Ho ho ho. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1145950&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1120452 ] Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Bugs item #1120452, was opened at 2005-02-11 01:04
Message generated for change (Comment added) made by complex
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470
>Category: Regular Expressions
Group: Python 2.4
Status: Open
Resolution: None
>Priority: 7
Submitted By: Viktor Ferenczi (complex)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Initial Comment:
Running the attached example crashes python 2.4.0 on linux (segfault) and
Windows. Python is compiled on Debian Linux 3.0r3 (Woody). On Windows XP, I
used the MSI installer downloaded from python.org
This may be a problem with the regular expression module, but I'm not sure.
Please assign a new category if it appears as a regexp bug.
This bug causes permanent crashes in my new WEB applications. Old apps not
using regexp and PyMeld seem to run correctly.
Thanks for 2.4.1.
--
>Comment By: Viktor Ferenczi (complex)
Date: 2005-02-22 14:07
Message:
Logged In: YES
user_id=142612
This bug is a segfault, a real crash using only the stock 2.4.0. It has been
reproduced correctly by jimjjewett. It seems to be a regexp related bug. I've
changed the category to pass this bug to a regexp expert. Thanks for any help.
- Complex
--
Comment By: Kurt B. Kaiser (kbk)
Date: 2005-02-20 02:56
Message:
Logged In: YES
user_id=149084
The restart in IDLE will occur if the subprocess is terminated or
segfaults.
--
Comment By: Jim Jewett (jimjjewett)
Date: 2005-02-11 20:55
Message:
Logged In: YES
user_id=764593
__gettattr__ alone can provoke the crash, if used several
times, and on sub-melds.
I can print both StreamURL1 and StreamURL2.
If I ask it for p.StreamURL2.src and p.StreamURL1.value,
it prints whichever one I ask for first, and then crashes on
the second. I did get it to print both (not assign, just
__getattr__) by first getting several other attributes from
p.StreamURL1, including some that didn't exist, so that
there was a raise AttributeError in between. Doing this a
half dozen times, I provoked a MemoryError.
"""
>>> p.StreamURL1.value
'mss://stream.url'
>>> p.StreamURL2.src
Traceback (most recent call last):
File "", line 1, in -toplevel-
p.StreamURL2.src
File "C:\Python24\Lib\site-packages\segfault240\PyMeld.
py", line 475, in __getattr__
start = self._findElementFromID(name)
File "C:\Python24\Lib\site-packages\segfault240\PyMeld.
py", line 425, in _findElementFromID
match = _findIDMatch(nodeID, subset)
File "C:\Python24\Lib\site-packages\segfault240\PyMeld.
py", line 282, in _findIDMatch
match = re.search(thisRE, text)
File "C:\Python24\lib\sre.py", line 134, in search
return _compile(pattern, flags).search(string)
MemoryError
>>>
"""
--
Comment By: Jim Jewett (jimjjewett)
Date: 2005-02-11 20:36
Message:
Logged In: YES
user_id=764593
Partially reproduced on Windows XP. (Using the stock 2.4.
0 msi)
Just loading it in IDLE and hitting F5 (run), it prints None,
as though it had succeeded perfectly.
Typing in the commands from index.py by hand, I can get
it to give me the "encountered an error; Tell Microsoft?"
box, but IDLE only restarts instead of actually crashing.
There seems to a problem between the __getattr__ and
the __setattr__ in PyMeld.
"""
>>> p=Meld(open('player.html','rb').read())
>>> p.StreamURL1.value
'mss://stream.url'
>>> p.StreamURL2
>>> p.StreamURL2.src
'mms://stream.url'
>>> v=Video()
>>> v.stream
's'
>>> p.StreamURL1.value=v.stream
>>> p.StreamURL1.value
>>>
RESTART
>>>
"""
--
Comment By: Michael Hudson (mwh)
Date: 2005-02-11 15:57
Message:
Logged In: YES
user_id=6656
What do you do to make it crash? "python index.py"?
It doesn't fail for me with CVS HEAD.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1146231 ] bsddb3 build problems on FreeBSD (2.4 + 2.5)
Bugs item #1146231, was opened at 2005-02-23 00:10 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=1146231&group_id=5470 Category: Build Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Andrew I MacIntyre (aimacintyre) Assigned to: Nobody/Anonymous (nobody) Summary: bsddb3 build problems on FreeBSD (2.4 + 2.5) Initial Comment: FreeBSD's ports system has another variation on naming the Sleepcat DB library. The attached patch adds support for this naming variation. The patch is actually for CVS head, but applies to the 2.4 maintenance branch (with an offset). In my particular case, my FreeBSD box has both DB 4.1 and DB 4.0 installed; the build was finding the 4.1 headers and compiling against them, but then linking to the 4.0 library. In consequence, all the tests which depend on the _bsddb module (test_anydbm, test_bsddb, test_bsddb185, test_shelve, test_whichdb) were failing or dumping core. This patch (or something with similar effect) should be applied in time for 2.4.1 in my opinion (I could do that, but would like the release manager's approval). -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1146231&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1120452 ] Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Bugs item #1120452, was opened at 2005-02-11 00:04
Message generated for change (Comment added) made by mwh
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470
Category: Regular Expressions
Group: Python 2.4
Status: Open
Resolution: None
Priority: 7
Submitted By: Viktor Ferenczi (complex)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Initial Comment:
Running the attached example crashes python 2.4.0 on linux (segfault) and
Windows. Python is compiled on Debian Linux 3.0r3 (Woody). On Windows XP, I
used the MSI installer downloaded from python.org
This may be a problem with the regular expression module, but I'm not sure.
Please assign a new category if it appears as a regexp bug.
This bug causes permanent crashes in my new WEB applications. Old apps not
using regexp and PyMeld seem to run correctly.
Thanks for 2.4.1.
--
>Comment By: Michael Hudson (mwh)
Date: 2005-02-22 14:51
Message:
Logged In: YES
user_id=6656
Well, I still can't make it crash. Can one of you provide a crashing driver
script? Better still would be finding which regexp and which input is the
problem.
(Unless it's a memory-scribble random crasher type bug...)
--
Comment By: Viktor Ferenczi (complex)
Date: 2005-02-22 13:07
Message:
Logged In: YES
user_id=142612
This bug is a segfault, a real crash using only the stock 2.4.0. It has been
reproduced correctly by jimjjewett. It seems to be a regexp related bug. I've
changed the category to pass this bug to a regexp expert. Thanks for any help.
- Complex
--
Comment By: Kurt B. Kaiser (kbk)
Date: 2005-02-20 01:56
Message:
Logged In: YES
user_id=149084
The restart in IDLE will occur if the subprocess is terminated or
segfaults.
--
Comment By: Jim Jewett (jimjjewett)
Date: 2005-02-11 19:55
Message:
Logged In: YES
user_id=764593
__gettattr__ alone can provoke the crash, if used several
times, and on sub-melds.
I can print both StreamURL1 and StreamURL2.
If I ask it for p.StreamURL2.src and p.StreamURL1.value,
it prints whichever one I ask for first, and then crashes on
the second. I did get it to print both (not assign, just
__getattr__) by first getting several other attributes from
p.StreamURL1, including some that didn't exist, so that
there was a raise AttributeError in between. Doing this a
half dozen times, I provoked a MemoryError.
"""
>>> p.StreamURL1.value
'mss://stream.url'
>>> p.StreamURL2.src
Traceback (most recent call last):
File "", line 1, in -toplevel-
p.StreamURL2.src
File "C:\Python24\Lib\site-packages\segfault240\PyMeld.
py", line 475, in __getattr__
start = self._findElementFromID(name)
File "C:\Python24\Lib\site-packages\segfault240\PyMeld.
py", line 425, in _findElementFromID
match = _findIDMatch(nodeID, subset)
File "C:\Python24\Lib\site-packages\segfault240\PyMeld.
py", line 282, in _findIDMatch
match = re.search(thisRE, text)
File "C:\Python24\lib\sre.py", line 134, in search
return _compile(pattern, flags).search(string)
MemoryError
>>>
"""
--
Comment By: Jim Jewett (jimjjewett)
Date: 2005-02-11 19:36
Message:
Logged In: YES
user_id=764593
Partially reproduced on Windows XP. (Using the stock 2.4.
0 msi)
Just loading it in IDLE and hitting F5 (run), it prints None,
as though it had succeeded perfectly.
Typing in the commands from index.py by hand, I can get
it to give me the "encountered an error; Tell Microsoft?"
box, but IDLE only restarts instead of actually crashing.
There seems to a problem between the __getattr__ and
the __setattr__ in PyMeld.
"""
>>> p=Meld(open('player.html','rb').read())
>>> p.StreamURL1.value
'mss://stream.url'
>>> p.StreamURL2
>>> p.StreamURL2.src
'mms://stream.url'
>>> v=Video()
>>> v.stream
's'
>>> p.StreamURL1.value=v.stream
>>> p.StreamURL1.value
>>>
RESTART
>>>
"""
--
Comment By: Michael Hudson (mwh)
Date: 2005-02-11 14:57
Message:
Logged In: YES
user_id=6656
What do you do to make it crash? "python index.py"?
It doesn't fail for me with CVS HEAD.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1120452 ] Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Bugs item #1120452, was opened at 2005-02-11 01:04 Message generated for change (Comment added) made by complex You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470 Category: Regular Expressions Group: Python 2.4 Status: Open Resolution: None Priority: 7 Submitted By: Viktor Ferenczi (complex) Assigned to: Nobody/Anonymous (nobody) Summary: Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED Initial Comment: Running the attached example crashes python 2.4.0 on linux (segfault) and Windows. Python is compiled on Debian Linux 3.0r3 (Woody). On Windows XP, I used the MSI installer downloaded from python.org This may be a problem with the regular expression module, but I'm not sure. Please assign a new category if it appears as a regexp bug. This bug causes permanent crashes in my new WEB applications. Old apps not using regexp and PyMeld seem to run correctly. Thanks for 2.4.1. -- >Comment By: Viktor Ferenczi (complex) Date: 2005-02-22 16:19 Message: Logged In: YES user_id=142612 Some additional information and summary: My machine is a 3.0Hz Intel P4 with 1Gbyte memory, without overclocking. I use 2 antivirus (1 active) and 3 antispyware apps + firewall. The memory has been tested for 6 hours with Knoppix's memtest without any error, so my machine can be considered to be stable. The attached script can crash python 2.4.0 at least for me and jumjjewett. Do not run the script from IDLE, since it can hide the segfault. I usually run my scripts from SciTE (see: www.scintilla.org ). The bug can be reproduced on stock Python 2.4.0 (MSI installer). PyMeld is pure python (uses only the standard library), no C extension modules used. I did not test this bug with the latest CVS versions of Python 2.4. Is produces segfault under Linux. I'll try to narrow down this bug for specific regex patterns. -- Comment By: Michael Hudson (mwh) Date: 2005-02-22 15:51 Message: Logged In: YES user_id=6656 Well, I still can't make it crash. Can one of you provide a crashing driver script? Better still would be finding which regexp and which input is the problem. (Unless it's a memory-scribble random crasher type bug...) -- Comment By: Viktor Ferenczi (complex) Date: 2005-02-22 14:07 Message: Logged In: YES user_id=142612 This bug is a segfault, a real crash using only the stock 2.4.0. It has been reproduced correctly by jimjjewett. It seems to be a regexp related bug. I've changed the category to pass this bug to a regexp expert. Thanks for any help. - Complex -- Comment By: Kurt B. Kaiser (kbk) Date: 2005-02-20 02:56 Message: Logged In: YES user_id=149084 The restart in IDLE will occur if the subprocess is terminated or segfaults. -- Comment By: Jim Jewett (jimjjewett) Date: 2005-02-11 20:55 Message: Logged In: YES user_id=764593 __gettattr__ alone can provoke the crash, if used several times, and on sub-melds. I can print both StreamURL1 and StreamURL2. If I ask it for p.StreamURL2.src and p.StreamURL1.value, it prints whichever one I ask for first, and then crashes on the second. I did get it to print both (not assign, just __getattr__) by first getting several other attributes from p.StreamURL1, including some that didn't exist, so that there was a raise AttributeError in between. Doing this a half dozen times, I provoked a MemoryError. """ >>> p.StreamURL1.value 'mss://stream.url' >>> p.StreamURL2.src Traceback (most recent call last): File "", line 1, in -toplevel- p.StreamURL2.src File "C:\Python24\Lib\site-packages\segfault240\PyMeld. py", line 475, in __getattr__ start = self._findElementFromID(name) File "C:\Python24\Lib\site-packages\segfault240\PyMeld. py", line 425, in _findElementFromID match = _findIDMatch(nodeID, subset) File "C:\Python24\Lib\site-packages\segfault240\PyMeld. py", line 282, in _findIDMatch match = re.search(thisRE, text) File "C:\Python24\lib\sre.py", line 134, in search return _compile(pattern, flags).search(string) MemoryError >>> """ -- Comment By: Jim Jewett (jimjjewett) Date: 2005-02-11 20:36 Message: Logged In: YES user_id=764593 Partially reproduced on Windows XP. (Using the stock 2.4. 0 msi) Just loading it in IDLE and hitting F5 (run), it prints None, as though it had succeeded perfectly. Typing in the commands from index.py by hand, I can get it to give me the "encountered an error; Tell Microsoft?" box, but IDLE only restarts instead of actually crashing. There seems to a problem between the __getattr__ and the __setattr__ i
[ python-Bugs-1147646 ] Windows deadlock with PyEval_ReleaseLock
Bugs item #1147646, was opened at 2005-02-22 11: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=1147646&group_id=5470 Category: Windows Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Lou Montulli (montulli) Assigned to: Nobody/Anonymous (nobody) Summary: Windows deadlock with PyEval_ReleaseLock Initial Comment: This problem is described well by this post from '03 http://mail.python.org/pipermail/python-dev/2003-August/037729.html The problem still seems to exist. The solution described within the post will not work in all cases because if you do not call PyEval_ReleaseLock then other threads will be deadlocked, and if you do call PyEval_ReleaseLock, the thread that originally called InitThreads will be deadlocked. The only work around that I have found so far is to use a separate thread that will never call scripts call InitThreads and then PyEval_ReleaseLock. After that all threads will run correctly, but the thread that originally called InitThreads cannot run python. Feel free to contact me for any other details, or call me a bonehead if I screwed something up. lou a montulli o org -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1147646&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1149413 ] fix bsddb documentation psize -> pgsize
Bugs item #1149413, was opened at 2005-02-22 23:14 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=1149413&group_id=5470 Category: Documentation Group: Python 2.3 Status: Open Resolution: None Priority: 5 Submitted By: Martin Mokrejs (mmokrejs) Assigned to: Nobody/Anonymous (nobody) Summary: fix bsddb documentation psize -> pgsize Initial Comment: Where: http://docs.python.org/lib/module-bsddb.html You say there: btopen( filename[, flag[, mode[, btflags[, cachesize[, maxkeypage[, minkeypage[, psize[, lorder) the word psize should be replaced with pgsize. An example would help: >>> d = bsddb.btopen(None, "c", cachesize=768000, pgsize=65536) >>> d = bsddb.btopen(None, "n", cachesize=768000, pgsize=65536) Traceback (most recent call last): File "", line 1, in ? File "/usr/lib/python2.3/bsddb/__init__.py", line 201, in btopen flags = _checkflag(flag, file) File "/usr/lib/python2.3/bsddb/__init__.py", line 249, in _checkflag if os.path.isfile(file): File "/usr/lib/python2.3/posixpath.py", line 200, in isfile st = os.stat(path) TypeError: coercing to Unicode: need string or buffer, NoneType found >>> The latter is I believe possibly a bug in the python wrapper not handling 'n' properly. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1149413&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1149447 ] bssdb wrapper does not export some low-level functions
Bugs item #1149447, was opened at 2005-02-23 00:15 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=1149447&group_id=5470 Category: Python Library Group: Python 2.3 Status: Open Resolution: None Priority: 5 Submitted By: Martin Mokrejs (mmokrejs) Assigned to: Nobody/Anonymous (nobody) Summary: bssdb wrapper does not export some low-level functions Initial Comment: If you go and read docs/api_c/db_list.html in any newer BerkelyDB source tree, you find some methods not exported in/usr/lib/python2.3/bsddb/__init__.py although at least some do exist in dbobj.py. For example, of my interrest were two mentioned in the patch. I believe someone should go and make sure they are present. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1149447&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1120452 ] Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Bugs item #1120452, was opened at 2005-02-10 19:04 Message generated for change (Comment added) made by jimjjewett You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470 Category: Regular Expressions Group: Python 2.4 Status: Open Resolution: None Priority: 7 Submitted By: Viktor Ferenczi (complex) Assigned to: Nobody/Anonymous (nobody) Summary: Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED Initial Comment: Running the attached example crashes python 2.4.0 on linux (segfault) and Windows. Python is compiled on Debian Linux 3.0r3 (Woody). On Windows XP, I used the MSI installer downloaded from python.org This may be a problem with the regular expression module, but I'm not sure. Please assign a new category if it appears as a regexp bug. This bug causes permanent crashes in my new WEB applications. Old apps not using regexp and PyMeld seem to run correctly. Thanks for 2.4.1. -- Comment By: Jim Jewett (jimjjewett) Date: 2005-02-22 18:58 Message: Logged In: YES user_id=764593 It probably is a memory scribble bug, though it might not be in re. For instance, the __getattr__ and __setattr__ try to do some shortcuts saving position, and they may cause the out- of-bounds. The crashes are very dependent on order. I wasn't kidding when I said it ran fine and printed None if run as a whole, but crashed when the same lines were input one by one. (Which gave idle a chance to do different things with memory in between, and didn't define a function object.) Also note that the second attribute access (even to a previously OK attribute) could cause a crash, unless it had had a chance to clear things up first -- but then it raised a MemoryError, when I almost certainly wasn't yet out of RAM. -- Comment By: Viktor Ferenczi (complex) Date: 2005-02-22 10:19 Message: Logged In: YES user_id=142612 Some additional information and summary: My machine is a 3.0Hz Intel P4 with 1Gbyte memory, without overclocking. I use 2 antivirus (1 active) and 3 antispyware apps + firewall. The memory has been tested for 6 hours with Knoppix's memtest without any error, so my machine can be considered to be stable. The attached script can crash python 2.4.0 at least for me and jumjjewett. Do not run the script from IDLE, since it can hide the segfault. I usually run my scripts from SciTE (see: www.scintilla.org ). The bug can be reproduced on stock Python 2.4.0 (MSI installer). PyMeld is pure python (uses only the standard library), no C extension modules used. I did not test this bug with the latest CVS versions of Python 2.4. Is produces segfault under Linux. I'll try to narrow down this bug for specific regex patterns. -- Comment By: Michael Hudson (mwh) Date: 2005-02-22 09:51 Message: Logged In: YES user_id=6656 Well, I still can't make it crash. Can one of you provide a crashing driver script? Better still would be finding which regexp and which input is the problem. (Unless it's a memory-scribble random crasher type bug...) -- Comment By: Viktor Ferenczi (complex) Date: 2005-02-22 08:07 Message: Logged In: YES user_id=142612 This bug is a segfault, a real crash using only the stock 2.4.0. It has been reproduced correctly by jimjjewett. It seems to be a regexp related bug. I've changed the category to pass this bug to a regexp expert. Thanks for any help. - Complex -- Comment By: Kurt B. Kaiser (kbk) Date: 2005-02-19 20:56 Message: Logged In: YES user_id=149084 The restart in IDLE will occur if the subprocess is terminated or segfaults. -- Comment By: Jim Jewett (jimjjewett) Date: 2005-02-11 14:55 Message: Logged In: YES user_id=764593 __gettattr__ alone can provoke the crash, if used several times, and on sub-melds. I can print both StreamURL1 and StreamURL2. If I ask it for p.StreamURL2.src and p.StreamURL1.value, it prints whichever one I ask for first, and then crashes on the second. I did get it to print both (not assign, just __getattr__) by first getting several other attributes from p.StreamURL1, including some that didn't exist, so that there was a raise AttributeError in between. Doing this a half dozen times, I provoked a MemoryError. """ >>> p.StreamURL1.value 'mss://stream.url' >>> p.StreamURL2.src Traceback (most recent call last): File "", line 1, in -toplevel- p.StreamURL2.src File "C:\Python24\Lib\site-packages\segfault240\PyMeld. py", line 475, in __getattr__ start = self._findElementFromID(name) File "C:\Python24\Lib\site-packages\segfault240\PyMeld. py", line 425,
[ python-Bugs-1149447 ] bssdb wrapper does not export some low-level functions
Bugs item #1149447, was opened at 2005-02-23 00:15 Message generated for change (Comment added) made by mmokrejs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1149447&group_id=5470 Category: Python Library Group: Python 2.3 Status: Open Resolution: None Priority: 5 Submitted By: Martin Mokrejs (mmokrejs) Assigned to: Nobody/Anonymous (nobody) Summary: bssdb wrapper does not export some low-level functions Initial Comment: If you go and read docs/api_c/db_list.html in any newer BerkelyDB source tree, you find some methods not exported in/usr/lib/python2.3/bsddb/__init__.py although at least some do exist in dbobj.py. For example, of my interrest were two mentioned in the patch. I believe someone should go and make sure they are present. -- >Comment By: Martin Mokrejs (mmokrejs) Date: 2005-02-23 01:01 Message: Logged In: YES user_id=696559 Please read docs/ref/env/db_config.html and allow users to specify the DB_CONFIG file to override any methods not expoerted through bsddb wrapper yet. Using that approach, user can alter many options available only when database is created! docs/ref/am_misc/tune.html docs/ref/am_misc/faq.html -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1149447&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
