[ python-Bugs-1077040 ] Error building _bsddb extension
Bugs item #1077040, was opened at 2004-12-01 12:19 Message generated for change (Comment added) made by greg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1077040&group_id=5470 Category: Build Group: Python 2.4 >Status: Closed >Resolution: Fixed Priority: 6 Submitted By: Oleg Broytmann (phd) Assigned to: Gregory P. Smith (greg) Summary: Error building _bsddb extension Initial Comment: Trying to build Python 2.4 on Debian GNU/Linux 3.0 using gcc 3.3.4. BerkeleyDB version is 3.2, header is /usr/include/db.h, library in /usr/lib. Error: gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -fPIC -I. -I/usr/local/src/Python/Python-2.4/./Include -I/usr/local/include -I/usr/local/src/Python/Python-2.4/Include -I/usr/local/src/Python/Python-2.4 -c /usr/local/src/Python/Python-2.4/Modules/_bsddb.c -o build/temp.linux-i686-2.4/_bsddb.o running build_scripts /usr/local/src/Python/Python-2.4/Modules/_bsddb.c: In function `DB_pget': /usr/local/src/Python/Python-2.4/Modules/_bsddb.c:1464: error: structure has no member named `pget' /usr/local/src/Python/Python-2.4/Modules/_bsddb.c:1482: error: structure has no member named `primaryDBType' /usr/local/src/Python/Python-2.4/Modules/_bsddb.c:1483: error: structure has no member named `primaryDBType' /usr/local/src/Python/Python-2.4/Modules/_bsddb.c: In function `DBC_pget': /usr/local/src/Python/Python-2.4/Modules/_bsddb.c:2928: error: structure has no member named `c_pget' /usr/local/src/Python/Python-2.4/Modules/_bsddb.c:2943: error: structure has no member named `primaryDBType' /usr/local/src/Python/Python-2.4/Modules/_bsddb.c:2944: error: structure has no member named `primaryDBType' -- >Comment By: Gregory P. Smith (greg) Date: 2004-12-16 01:52 Message: Logged In: YES user_id=413 fixed in python cvs both in HEAD and 2.4 (release24-maint branch). patch attached to this bug if you just want to apply it to your python 2.4 tarball. fwiw, its better to use a more recent version of berkeleydb if possible. -- Comment By: Gregory P. Smith (greg) Date: 2004-12-13 04:13 Message: Logged In: YES user_id=413 Yes this is easy to reproduce. At the moment the preferred workaround is to use a more recent version of BerkeleyDB <= 4.2 (4.3 support has not yet been committed to the 2.4 maintenance branch). I'll fix this so that 3.2 works again shortly. -- Comment By: Oleg Broytmann (phd) Date: 2004-12-12 02:47 Message: Logged In: YES user_id=4799 #define DB_VERSION_MAJOR3 #define DB_VERSION_MINOR2 #define DB_VERSION_PATCH9 #define DB_VERSION_STRING "Sleepycat Software: Berkeley DB 3.2.9: (April 7, 2002)" -- Comment By: Andrew I MacIntyre (aimacintyre) Date: 2004-12-12 01:23 Message: Logged In: YES user_id=250749 What are the DB_VERSION_MAJOR and DB_VERSION_MINOR macros defined to in your /usr/include/db.h? The primaryDBType symbol is only referenced in code compiled for DB versions 3.3 and higher, and the pget symbol is referenced in code compiled for DB 3.2 and higher. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1077040&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1084279 ] status of small floats in xml-rpc ?
Bugs item #1084279, was opened at 2004-12-13 05:07
Message generated for change (Comment added) made by rhettinger
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1084279&group_id=5470
Category: Python Library
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Antoine Pitrou (pitrou)
>Assigned to: Nobody/Anonymous (nobody)
Summary: status of small floats in xml-rpc ?
Initial Comment:
Hi,
I've been reading through the xmlrpclib.py code to see
that floats are marshalled the following way:
def dump_double(self, value, write):
write("")
write(repr(value))
write("\n")
dispatch[FloatType] = dump_double
Using repr() means that small or big floats, for
example, will be output using the exponent notation:
>>> repr(2**-15)
'3.0517578125e-05'
Unfortunately, the XML-RPC specification does not allow
this notation:
"At this time, only decimal point notation is allowed,
a plus or a minus, followed by any number of numeric
characters, followed by a period and any number of
numeric characters. Whitespace is not allowed. The
range of allowable values is implementation-dependent,
is not specified."
(http://www.xmlrpc.com/spec)
Thus floats marshalled using xmlrpclib may not be
readable using other XML-RPC implementations.
(I don't have any concrete data about this though)
--
>Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-16 05:32
Message:
Logged In: YES
user_id=80475
After more thought, I'm concerned that switching to full
decimal notation will break the guarantee eval(repr(x))==x.
Also, Skip's thoughts seem reasonable. Rather than
switching to a non-compact format, it may be best to way for
the spec to catchup with real implementations.
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-13 17:19
Message:
Logged In: YES
user_id=80475
Various slightly unsatisfactory answers:
* It started out that way because that's what C did.
* It stayed that way because no one has requested it
* It may be that outside of XMLRPC there are very few valid
use cases.
* Future needs can be met by the decimal module.
--
Comment By: Antoine Pitrou (pitrou)
Date: 2004-12-13 14:04
Message:
Logged In: YES
user_id=133955
I'm gonna ask a stupid question (I'm quite a beginner in
Python). Why isn't there a %f-life formatting code for doing
just what you wrote - printing the float in full precision
in non-exponent format ?
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-13 13:12
Message:
Logged In: YES
user_id=80475
The thought was "be liberal in what you accept and be strict
on was is emitted." Still, the question is valid.
For C, it looks like strtod() is at the root of everything
converting from floats. The spec lays no limits on the
input format (exponents vs full decimal representation).
Instead, it just checks that the result is inside the range
of representable values and did not underflow.
Some experiments with MSC6 confirm that the full range may
be entered as regular decimals. Experiments with Perl show
the same result. I suspect all TCL and Ruby also have
strtod() at the core.
--
Comment By: Skip Montanaro (montanaro)
Date: 2004-12-13 10:38
Message:
Logged In: YES
user_id=44345
I understand what you''re doing, but I wonder if in the
process interoperability with other XML-RPC implementations
might actually get worse. While the spec doesn't support
exponential notation, most programming languages do, and
probably happily accept "1.234e-147" as a floating point
input. Python seems not to have problems accepting floating
point inputs with huge numbers of zeroes before or after the
decimal point, but other languages may not be quite so
forgiving. I think we need to be a bit careful before
changing our implementation. At the very least we should
probably verify the acceptance of non_e_repr-generated
strings by a few other languages commonly used with XML-RPC
(C, Perl, Tcl, Ruby?).
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-13 08:13
Message:
Logged In: YES
user_id=80475
See attached patch.
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-13 07:40
Message:
Logged In: YES
user_id=80475
I loaded a recipe for a helper function that meets the spec:
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/358361
Inserting and applying the helper function ought to be
backwards compatible (the new encoding is readable by
previous versions).
Martin, do you agree with appro
[ python-Bugs-1085861 ] subprocess.Popen feature request
Bugs item #1085861, was opened at 2004-12-15 10:33 Message generated for change (Settings changed) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085861&group_id=5470 Category: Python Library Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Michele Simionato (michele_s) >Assigned to: Peter Åstrand (astrand) Summary: subprocess.Popen feature request Initial Comment: I asked on comp.lang.python for a "kill" method in the Popen class. The answer was "the kill method is missing since it is not portable to Windows". However I got this message from Fredrik Lund """ I suggest filing a "bug" report about this. the Unix version is trivial, as you noticed, and it shouldn't take many minutes to add a TerminateProcess helper to _subprocess. """ So, I am following his suggestion ;-) Michele Simionato -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085861&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1085861 ] subprocess.Popen feature request
Bugs item #1085861, was opened at 2004-12-15 10:33 Message generated for change (Settings changed) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085861&group_id=5470 Category: Python Library >Group: Python 2.5 Status: Open Resolution: None Priority: 5 Submitted By: Michele Simionato (michele_s) Assigned to: Peter Åstrand (astrand) Summary: subprocess.Popen feature request Initial Comment: I asked on comp.lang.python for a "kill" method in the Popen class. The answer was "the kill method is missing since it is not portable to Windows". However I got this message from Fredrik Lund """ I suggest filing a "bug" report about this. the Unix version is trivial, as you noticed, and it shouldn't take many minutes to add a TerminateProcess helper to _subprocess. """ So, I am following his suggestion ;-) Michele Simionato -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085861&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1085172 ] Uninstaller should restore file associations if possible
Bugs item #1085172, was opened at 2004-12-14 10:13 Message generated for change (Settings changed) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085172&group_id=5470 Category: Installation Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Giles Antonio Radford (mewf) >Assigned to: Martin v. Löwis (loewis) Summary: Uninstaller should restore file associations if possible Initial Comment: On installing on Windows, the Python installer associates .py and .pyw files to the new installation of python. The installer should cache the previous associations, and in the event of uninstallation restore them to their previous values if the application the are associated with still exists. This allows for easier migration back to 2.3 in this case, but also for easier back migration in the case of installing a beta version of python 2.5 or whatever in the future. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085172&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1080864 ] locale.py doesn't recognize valid locale setting
Bugs item #1080864, was opened at 2004-12-07 21:23 Message generated for change (Comment added) made by childsplay You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1080864&group_id=5470 Category: Python Library Group: Python 2.3 Status: Closed Resolution: Fixed Priority: 5 Submitted By: stas Z (childsplay) Assigned to: M.-A. Lemburg (lemburg) Summary: locale.py doesn't recognize valid locale setting Initial Comment: [EMAIL PROTECTED]:~$ locale LANG=nb_NO [...] [EMAIL PROTECTED]:~$ python Python 2.3.4 (#2, Sep 24 2004, 08:39:09) [GCC 3.3.4 (Debian 1:3.3.4-12)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import locale >>> locale.getdefaultlocale() Traceback (most recent call last): File "", line 1, in ? File "/usr/lib/python2.3/locale.py", line 346, in getdefaultlocale return _parse_localename(localename) File "/usr/lib/python2.3/locale.py", line 280, in _parse_localename raise ValueError, 'unknown locale: %s' % localename ValueError: unknown locale: nb_NO >>> -- >Comment By: stas Z (childsplay) Date: 2004-12-16 13:33 Message: Logged In: YES user_id=638376 Checked and it works ok, thanks. -- Comment By: M.-A. Lemburg (lemburg) Date: 2004-12-13 20:58 Message: Logged In: YES user_id=38388 Thanks. I've noticed that the C lib doesn't seem to like "UTF-8" but works well with "UTF8" (no hyphen). Checking in Lib/locale.py; /cvsroot/python/python/dist/src/Lib/locale.py,v <-- locale.py new revision: 1.30; previous revision: 1.29 done Checking in Tools/i18n/makelocalealias.py; /cvsroot/python/python/dist/src/Tools/i18n/makelocalealias.py,v <-- makelocalealias.py new revision: 1.2; previous revision: 1.1 done Please check again with the updated version. -- Comment By: stas Z (childsplay) Date: 2004-12-11 17:18 Message: Logged In: YES user_id=638376 I've looked at the CVS/locale.py but is the utf8 entry missing? Don't know about the X alias mapping, but I suspect that there should also be an utf8 entry also for nb_NO/nn_NO. (Just as there is for no_NO) -- Comment By: M.-A. Lemburg (lemburg) Date: 2004-12-10 22:58 Message: Logged In: YES user_id=38388 Checking in Lib/locale.py; /cvsroot/python/python/dist/src/Lib/locale.py,v <-- locale.py new revision: 1.29; previous revision: 1.28 done -- Comment By: M.-A. Lemburg (lemburg) Date: 2004-12-10 14:16 Message: Logged In: YES user_id=38388 Well, if the alias mapping is good enough for X, then it's good enough for me :-) I think we ought to update the alias table with the current data of the X locale.alias file. This file also includes the mappings that childsplay mentioned. There also seems to be a bug in the encoding alias table: "utf" is no longer recognized by setlocale(). This should be changed to "utf8". I'll fix that and post an update here. -- Comment By: Martin v. Löwis (loewis) Date: 2004-12-10 00:26 Message: Logged In: YES user_id=21627 getdefaultencoding might be "targeted" at the OS level - but the implementation certainly is not. On the OS level, the C library will often use a different encoding after locale.setlocale(locale.LC_ALL,"") is called, compared to what getdefaultencoding returns. The approach takien inside getdefaultencoding is inherently flawed, and cannot possibly work in all cases; getpreferredencoding fixes that flaw. -- Comment By: M.-A. Lemburg (lemburg) Date: 2004-12-09 10:56 Message: Logged In: YES user_id=38388 childsplay (I wish people would use real names on SF...): We can add the aliases you gave below, but we need some URLs to add as reference. Please provide this information, so that we can document that the aliases are in common use and why iso-8859-1 is their usually used encoding. Thanks. -- Comment By: M.-A. Lemburg (lemburg) Date: 2004-12-09 10:42 Message: Logged In: YES user_id=38388 Martin: "default" as opposed to whatever locale setting is currently active for the program, i.e. the locale setting the program would see after a single call to setlocale(LC_ALL, "") right after the start of the program. getdefaultlocale() mimics the lookup mechanism of setlocale(LC_ALL, ""). The fact that the alias table may sometimes not give the correct encoding is not a fault of Python or the table - if the user wants to see a different encoding used as default encoding for the set locale, then the user should include that information in the LANG (or other
[ python-Bugs-518846 ] exception cannot be new-style class
Bugs item #518846, was opened at 2002-02-17 21:09 Message generated for change (Comment added) made by loewis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=518846&group_id=5470 Category: Type/class unification Group: Python 2.3 Status: Open Resolution: None Priority: 5 Submitted By: Magnus Heino (magnusheino) Assigned to: Guido van Rossum (gvanrossum) Summary: exception cannot be new-style class Initial Comment: [EMAIL PROTECTED] magnus]$ python2.2 Python 2.2 (#1, Jan 26 2002, 14:27:24) [GCC 2.96 2731 (Red Hat Linux 7.1 2.96-98)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> class foo(object): ... pass ... >>> raise foo() Traceback (most recent call last): File "", line 1, in ? TypeError: exceptions must be strings, classes, or instances, not foo >>> -- >Comment By: Martin v. Löwis (loewis) Date: 2004-12-16 14:00 Message: Logged In: YES user_id=21627 This statement, as literally made, is incorrect: >>> class X(Exception): ... pass ... >>> e=X() >>> type(e) >>> raise e Traceback (most recent call last): File "", line 1, in ? __main__.X: <__main__.X instance at 0x401f2b4c> In this example, type(e) works, and x is an object which has Exception among its base classes. Still, I can throw x, despite your claim that I cannot. Even if I interpret your statement more literally (i.e. that you are talking about objects for which type(e) is a new-style class): Why do you think this statement explains there is a bug? As for why it is a new feature: it currently doesn't work, and anybody trying it will quickly find out that it doesn't work. The language reference says it doesn't work. The TypeError you get says it doesn't work. So that it doesn't work is clearly intentional; changing it will be a new feature. Notice that it is very difficult to implement this feature, as something needs to happen with strings and subtypes of str. Currently, string exceptions are caught by identity. If arbitrary objects can be used as exceptions, then strings should also be caught by type, not by identity; this is a backwards-incompatible change. A clean solution would be to deprecate string exceptions in 2.5, completely ban them in 2.6, and allow arbitrary objects to act as exceptions in 2.7. Please do read the entire thread of this RFE. -- Comment By: Robey Pointer (robey1) Date: 2004-12-16 00:39 Message: Logged In: YES user_id=1179122 Let me try to rephrase the problem so that it's obvious that this is a bug, and not a feature: 'type(e)' on an exception will not work in 2.3, and cannot be made to work from within python code. There's no way to throw an exception (ie an object with Exception in its ancestor list) that 'type(e)' will work on. :( -- Comment By: Martin v. Löwis (loewis) Date: 2004-12-15 22:59 Message: Logged In: YES user_id=21627 Whatever the solution to this problem, it is for sure that 2.4.x won't see it, because it will be a new feature. -- Comment By: Robey Pointer (robey1) Date: 2004-12-15 22:08 Message: Logged In: YES user_id=1179122 This caused me an hour of debugging a few nights ago. When using unified types, it's very confusing to find that not only does Exception not follow new-style object semantics, but it *can't*. Doing the obvious hack: class MyException (Exception, object): pass does not work! The interpreter (2.3) refuses to let you raise a unified-type object. And if you subclass exclusively from Exception, type(obj) returns 'instance' instead of the class (due to being an old-style object). Please fix this for 2.4! -- Comment By: Facundo Batista (facundobatista) Date: 2004-11-25 03:05 Message: Logged In: YES user_id=752496 Reproduced the bug in Py2.3. I think that this is a bug, at least because we "encourage" users to derive exceptions from Exception, so they should be able to not do it. The moment we say that they "must" derive from Exception, this can be closed (of course, this is my *very* personal opinion, ;) -- Comment By: Phillip J. Eby (pje) Date: 2002-07-11 22:12 Message: Logged In: YES user_id=56214 Just to make things even more interesting, the current 'raise' code *will* let you raise a new-style instance that derives from 'tuple'... of course, what it actually raises is the first element of said tuple-like thing. It seems to me that the very first thing that should be checked is whether the first argument to 'raise' is an instance of Exception, and if so, take its type and go from there. This would support both old and new-sty
[ python-Bugs-1085208 ] Installation ends prematurely
Bugs item #1085208, was opened at 2004-12-14 17:18
Message generated for change (Comment added) made by loewis
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085208&group_id=5470
Category: Installation
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: anamh0001 (anamh0001)
Assigned to: Nobody/Anonymous (nobody)
Summary: Installation ends prematurely
Initial Comment:
Test machine:
Pentium 4M 1.7Ghz
Win XP Pro w/ SP2
512Mb RAM
30Gb HD
.Net Framework 1.0 and 1.1
Windows Scripting Host 5.6
After double clicking the installation file. It proceeds to
act like any other Windows Installer. After accepting
c:\Python24 as the install directory, I am presented with
this screen saying that there was an error and that the
installation has ended prematurely.
FYI, I tried to install over Python 2.3 (as in upgrade) but
I got the same error. So I proceeded to uninstall Python
2.3 and other installed libraries. I then restarted the PC
and tried to install Python 2.4 again. This bug is the
symptom of this second try.
Please find the screenshot attached showing the final
screen.
--
>Comment By: Martin v. Löwis (loewis)
Date: 2004-12-16 14:07
Message:
Logged In: YES
user_id=21627
Can you please try the following things?
1. Run the script
== SNIP
Function CheckDir()
Set FSO = CreateObject("Scripting.FileSystemObject")
if FSO.FolderExists("c:\python24") then
wscript.echo "1"
else
wscript.echo "0"
end if
End Function
CheckDir()
= SNIP ==
in wscript.exe (i.e. save it into c:\x.vbs, then run c:\x.vbs)
2. Report the version of
C:\WINDOWS\SYSTEM32\wscript.exe
(5.6 is too imprecise - could it be that you have 5.6.0.8820?)
3. Install VBScript, from
http://www.microsoft.com/downloads/details.aspx?FamilyId=C717D943
-7E4B-4622-86EB-95A22B832CAA&displaylang=en
--
Comment By: anamh0001 (anamh0001)
Date: 2004-12-16 11:04
Message:
Logged In: YES
user_id=1178107
Please find the msi log file attached.
I managed to pinpoint the area where it breaks.. It's failing
on CheckDir with an error 2896.
-
MSI (c) (88:54) [09:50:38:430]: Doing action: CheckDir
Action start 09:50:38: CheckDir.
MSI (c) (88:3C) [09:50:38:440]: Cloaking enabled.
MSI (c) (88:3C) [09:50:38:440]: Attempting to enable all
disabled priveleges before calling Install on Server
MSI (c) (88:3C) [09:50:38:440]: Connected to service for CA
interface.
MSI (c) (88:88) [09:50:38:580]: Entering
MsiProvideComponentFromDescriptor. Descriptor: 2eAq^]D2g
(8V7Xaq(hoRIngresDBMS>M5KDYSUnf(HA*L[xeX)y, PathBuf:
1C4F348, pcchPathBuf: 1C4F344, pcchArgsOffset: 1C4F2A4
MSI (c) (88:88) [09:50:38:580]:
MsiProvideComponentFromDescriptor called for component
{997FA962-E067-11D1-9396-00A0C90F27F9}: returning
harcoded oleaut32.dll value
MSI (c) (88:88) [09:50:38:580]:
MsiProvideComponentFromDescriptor is returning: 0
Action ended 09:50:38: CheckDir. Return value 3.
MSI (c) (88:54) [09:50:38:921]: Note: 1: 2262 2: Error 3: -
2147287038
DEBUG: Error 2896: Executing action CheckDir failed.
The installer has encountered an unexpected error installing
this package. This may indicate a problem with this package.
The error code is 2896. The arguments are: CheckDir, ,
Action ended 09:50:38: SelectDirectoryDlg. Return value 3.
MSI (c) (88:94) [09:50:38:931]: Doing action: FatalError
Action start 09:50:38: FatalError.
Action 09:50:38: FatalError. Dialog created
Action ended 09:50:39: FatalError. Return value 2.
Action ended 09:50:40: INSTALL. Return value 3.
MSI (c) (88:94) [09:50:40:012]: Destroying RemoteAPI
object.
MSI (c) (88:3C) [09:50:40:012]: Custom Action Manager
thread ending.
--
Comment By: Martin v. Löwis (loewis)
Date: 2004-12-15 23:35
Message:
Logged In: YES
user_id=21627
Can you please run
msiexec /i python-2.4.msi /l*v python.log
and attach the resulting python.log (do NOT paste it into
the SF comment box).
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085208&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1085172 ] Uninstaller should restore file associations if possible
Bugs item #1085172, was opened at 2004-12-14 16:13 Message generated for change (Comment added) made by loewis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085172&group_id=5470 Category: Installation Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Giles Antonio Radford (mewf) Assigned to: Martin v. Löwis (loewis) Summary: Uninstaller should restore file associations if possible Initial Comment: On installing on Windows, the Python installer associates .py and .pyw files to the new installation of python. The installer should cache the previous associations, and in the event of uninstallation restore them to their previous values if the application the are associated with still exists. This allows for easier migration back to 2.3 in this case, but also for easier back migration in the case of installing a beta version of python 2.5 or whatever in the future. -- >Comment By: Martin v. Löwis (loewis) Date: 2004-12-16 14:09 Message: Logged In: YES user_id=21627 This is not possible to implement. If you want to not add associations for 2.4, you need to uncheck the "Register Extensions" feature in the installer UI. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085172&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1083793 ] Python 2.4 crashes
Bugs item #1083793, was opened at 2004-12-12 10:25
Message generated for change (Comment added) made by axel_kaiser
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1083793&group_id=5470
Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Axel Kaiser (axel_kaiser)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python 2.4 crashes
Initial Comment:
The new Python 2.4 crashes when starting some of my
programs. This happens under win xp as well as under
win nt. The crashes are reproduceble, but I didn't
succeed in finding the exact place where it happens.
In the attachment you find a Dr. Watson logfile. I hope
it helps. Otherwise I think I will be able to help with
more information.
Thanks in advance
Axel Kaiser
Germany
--
>Comment By: Axel Kaiser (axel_kaiser)
Date: 2004-12-16 14:56
Message:
Logged In: YES
user_id=1176563
Okay, I finally was able to produce a small example. When I
start python from the commandline with
file "Lebenserwartung.py" python crashes. It doesn't crash
when I remove the coding-line (1st line) of
file "Sterbetafeln.py".
(The example can't run properly due to missing files, but
these don't influence the crashes)
Best regards, Axel
--
Comment By: Martin v. Löwis (loewis)
Date: 2004-12-15 23:39
Message:
Logged In: YES
user_id=21627
Can you create a small test case that demonstrates the problem?
--
Comment By: Axel Kaiser (axel_kaiser)
Date: 2004-12-15 21:58
Message:
Logged In: YES
user_id=1176563
Sorry, the attachment was not appended. By the way, the
problem occurs without any external modules/libraries. It
just juses python-source. The problem might be connected
with the use of module array.
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-15 19:02
Message:
Logged In: YES
user_id=80475
Any objections to marking this as Invalid and closing the bug?
--
Comment By: Wolfgang Langner (tds33)
Date: 2004-12-15 16:16
Message:
Logged In: YES
user_id=600792
The FILE pointer is specific to your c-lib.
Different versions of the ms c-lib have incompatible
implementations of this structure.
To work arround such problems use python to get the right FILE*
Example (not tested):
/* use pythons std c library to produce a FILE object
to avoid mess with different c libs in debug or release mode
and different versions used to compile python
*/
PyObject* pyFile = PyFile_FromString(fileName, "r");
FILE* const file = PyFile_AsFile(pyFile);
assert(0 != file);
const int succ = PyRun_SimpleFile(file, fileName);
// now remove py file object
Py_XDECREF(pyFile);
--
Comment By: salyee (salyee)
Date: 2004-12-15 07:17
Message:
Logged In: YES
user_id=1178573
I have the same or similar problem.
While python24.dll(Python 2.4 for Windows) uses msvcr71.dll
for CRT, host C++ program embeding Python 2.4 as a script
engine, in my project, is compiled by VC++ 6.0 (msvcrt.dll).
So, the following code snip makes a crash.
FILE* fp = fopen("somecode.py", "rt"); // uses msvcrt.dll
PyRun_SimpleFile(fp, "somecode.py); // uses msvcr71.dll
inside. Cause of a crash.
In my case, I must use VC++ 6.0 and I want clients of my
program to install Python 2.4 from www.python.org.
How do I solve this problem ?
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-12 10:56
Message:
Logged In: YES
user_id=80475
The attachment didn't make it.
Be sure to check the upload box or it won't make it.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1083793&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1083793 ] Python 2.4 crashes
Bugs item #1083793, was opened at 2004-12-12 10:25
Message generated for change (Comment added) made by doerwalter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1083793&group_id=5470
Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Axel Kaiser (axel_kaiser)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python 2.4 crashes
Initial Comment:
The new Python 2.4 crashes when starting some of my
programs. This happens under win xp as well as under
win nt. The crashes are reproduceble, but I didn't
succeed in finding the exact place where it happens.
In the attachment you find a Dr. Watson logfile. I hope
it helps. Otherwise I think I will be able to help with
more information.
Thanks in advance
Axel Kaiser
Germany
--
>Comment By: Walter Dörwald (doerwalter)
Date: 2004-12-16 15:34
Message:
Logged In: YES
user_id=89016
This sounds like it might be related to bug
http://www.python.org/sf/1076985. Can you retry your
scripts with the patch from
http://www.python.org/sf/1076985? What happens if you
replace the "cp1252" in the encoding header with "iso-8859-
1"?
A quick workaround might be to wrap the long source lines in
Sterbetafeln.py.
--
Comment By: Axel Kaiser (axel_kaiser)
Date: 2004-12-16 14:56
Message:
Logged In: YES
user_id=1176563
Okay, I finally was able to produce a small example. When I
start python from the commandline with
file "Lebenserwartung.py" python crashes. It doesn't crash
when I remove the coding-line (1st line) of
file "Sterbetafeln.py".
(The example can't run properly due to missing files, but
these don't influence the crashes)
Best regards, Axel
--
Comment By: Martin v. Löwis (loewis)
Date: 2004-12-15 23:39
Message:
Logged In: YES
user_id=21627
Can you create a small test case that demonstrates the problem?
--
Comment By: Axel Kaiser (axel_kaiser)
Date: 2004-12-15 21:58
Message:
Logged In: YES
user_id=1176563
Sorry, the attachment was not appended. By the way, the
problem occurs without any external modules/libraries. It
just juses python-source. The problem might be connected
with the use of module array.
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-15 19:02
Message:
Logged In: YES
user_id=80475
Any objections to marking this as Invalid and closing the bug?
--
Comment By: Wolfgang Langner (tds33)
Date: 2004-12-15 16:16
Message:
Logged In: YES
user_id=600792
The FILE pointer is specific to your c-lib.
Different versions of the ms c-lib have incompatible
implementations of this structure.
To work arround such problems use python to get the right FILE*
Example (not tested):
/* use pythons std c library to produce a FILE object
to avoid mess with different c libs in debug or release mode
and different versions used to compile python
*/
PyObject* pyFile = PyFile_FromString(fileName, "r");
FILE* const file = PyFile_AsFile(pyFile);
assert(0 != file);
const int succ = PyRun_SimpleFile(file, fileName);
// now remove py file object
Py_XDECREF(pyFile);
--
Comment By: salyee (salyee)
Date: 2004-12-15 07:17
Message:
Logged In: YES
user_id=1178573
I have the same or similar problem.
While python24.dll(Python 2.4 for Windows) uses msvcr71.dll
for CRT, host C++ program embeding Python 2.4 as a script
engine, in my project, is compiled by VC++ 6.0 (msvcrt.dll).
So, the following code snip makes a crash.
FILE* fp = fopen("somecode.py", "rt"); // uses msvcrt.dll
PyRun_SimpleFile(fp, "somecode.py); // uses msvcr71.dll
inside. Cause of a crash.
In my case, I must use VC++ 6.0 and I want clients of my
program to install Python 2.4 from www.python.org.
How do I solve this problem ?
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-12 10:56
Message:
Logged In: YES
user_id=80475
The attachment didn't make it.
Be sure to check the upload box or it won't make it.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1083793&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1085208 ] Installation ends prematurely
Bugs item #1085208, was opened at 2004-12-14 16:18
Message generated for change (Comment added) made by anamh0001
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085208&group_id=5470
Category: Installation
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: anamh0001 (anamh0001)
Assigned to: Nobody/Anonymous (nobody)
Summary: Installation ends prematurely
Initial Comment:
Test machine:
Pentium 4M 1.7Ghz
Win XP Pro w/ SP2
512Mb RAM
30Gb HD
.Net Framework 1.0 and 1.1
Windows Scripting Host 5.6
After double clicking the installation file. It proceeds to
act like any other Windows Installer. After accepting
c:\Python24 as the install directory, I am presented with
this screen saying that there was an error and that the
installation has ended prematurely.
FYI, I tried to install over Python 2.3 (as in upgrade) but
I got the same error. So I proceeded to uninstall Python
2.3 and other installed libraries. I then restarted the PC
and tried to install Python 2.4 again. This bug is the
symptom of this second try.
Please find the screenshot attached showing the final
screen.
--
>Comment By: anamh0001 (anamh0001)
Date: 2004-12-16 15:21
Message:
Logged In: YES
user_id=1178107
BUG FIXED -- solution below.
1)
BTW I actually thought the installer was looking for
c:\python24. So I created the folder before running the
installer again. But it didnt work.
When I ran the script. It returned this error: I used cscript.
c:\x.vbs(2, 7) (null): The specified module could not be found.
2) The version of wscript and cscript is 5.6.0.8825
3) This is latest version because I read that installing the
latest version of scripting host fixes installation problems.
I managed to fix it. I registered scrrun.dll by typing:
regsvr32 c:\windows\system32\scrrun.dll
Thanks for all the help..
--
Comment By: Martin v. Löwis (loewis)
Date: 2004-12-16 13:07
Message:
Logged In: YES
user_id=21627
Can you please try the following things?
1. Run the script
== SNIP
Function CheckDir()
Set FSO = CreateObject("Scripting.FileSystemObject")
if FSO.FolderExists("c:\python24") then
wscript.echo "1"
else
wscript.echo "0"
end if
End Function
CheckDir()
= SNIP ==
in wscript.exe (i.e. save it into c:\x.vbs, then run c:\x.vbs)
2. Report the version of
C:\WINDOWS\SYSTEM32\wscript.exe
(5.6 is too imprecise - could it be that you have 5.6.0.8820?)
3. Install VBScript, from
http://www.microsoft.com/downloads/details.aspx?FamilyId=C717D943
-7E4B-4622-86EB-95A22B832CAA&displaylang=en
--
Comment By: anamh0001 (anamh0001)
Date: 2004-12-16 10:04
Message:
Logged In: YES
user_id=1178107
Please find the msi log file attached.
I managed to pinpoint the area where it breaks.. It's failing
on CheckDir with an error 2896.
-
MSI (c) (88:54) [09:50:38:430]: Doing action: CheckDir
Action start 09:50:38: CheckDir.
MSI (c) (88:3C) [09:50:38:440]: Cloaking enabled.
MSI (c) (88:3C) [09:50:38:440]: Attempting to enable all
disabled priveleges before calling Install on Server
MSI (c) (88:3C) [09:50:38:440]: Connected to service for CA
interface.
MSI (c) (88:88) [09:50:38:580]: Entering
MsiProvideComponentFromDescriptor. Descriptor: 2eAq^]D2g
(8V7Xaq(hoRIngresDBMS>M5KDYSUnf(HA*L[xeX)y, PathBuf:
1C4F348, pcchPathBuf: 1C4F344, pcchArgsOffset: 1C4F2A4
MSI (c) (88:88) [09:50:38:580]:
MsiProvideComponentFromDescriptor called for component
{997FA962-E067-11D1-9396-00A0C90F27F9}: returning
harcoded oleaut32.dll value
MSI (c) (88:88) [09:50:38:580]:
MsiProvideComponentFromDescriptor is returning: 0
Action ended 09:50:38: CheckDir. Return value 3.
MSI (c) (88:54) [09:50:38:921]: Note: 1: 2262 2: Error 3: -
2147287038
DEBUG: Error 2896: Executing action CheckDir failed.
The installer has encountered an unexpected error installing
this package. This may indicate a problem with this package.
The error code is 2896. The arguments are: CheckDir, ,
Action ended 09:50:38: SelectDirectoryDlg. Return value 3.
MSI (c) (88:94) [09:50:38:931]: Doing action: FatalError
Action start 09:50:38: FatalError.
Action 09:50:38: FatalError. Dialog created
Action ended 09:50:39: FatalError. Return value 2.
Action ended 09:50:40: INSTALL. Return value 3.
MSI (c) (88:94) [09:50:40:012]: Destroying RemoteAPI
object.
MSI (c) (88:3C) [09:50:40:012]: Custom Action Manager
thread ending.
--
Comment By: Martin v. Löwis (loewis)
Date: 2004-12-15 22:35
Message:
Logged In: YES
user_id=21627
Can you please run
msiexec /i python-2.4.msi /l*v python.log
and attach the resulting python.log (do NOT paste it into
the SF comment bo
[ python-Bugs-1085208 ] Installation ends prematurely
Bugs item #1085208, was opened at 2004-12-14 17:18
Message generated for change (Settings changed) made by loewis
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085208&group_id=5470
Category: Installation
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: anamh0001 (anamh0001)
>Assigned to: Martin v. Löwis (loewis)
Summary: Installation ends prematurely
Initial Comment:
Test machine:
Pentium 4M 1.7Ghz
Win XP Pro w/ SP2
512Mb RAM
30Gb HD
.Net Framework 1.0 and 1.1
Windows Scripting Host 5.6
After double clicking the installation file. It proceeds to
act like any other Windows Installer. After accepting
c:\Python24 as the install directory, I am presented with
this screen saying that there was an error and that the
installation has ended prematurely.
FYI, I tried to install over Python 2.3 (as in upgrade) but
I got the same error. So I proceeded to uninstall Python
2.3 and other installed libraries. I then restarted the PC
and tried to install Python 2.4 again. This bug is the
symptom of this second try.
Please find the screenshot attached showing the final
screen.
--
Comment By: anamh0001 (anamh0001)
Date: 2004-12-16 16:21
Message:
Logged In: YES
user_id=1178107
BUG FIXED -- solution below.
1)
BTW I actually thought the installer was looking for
c:\python24. So I created the folder before running the
installer again. But it didnt work.
When I ran the script. It returned this error: I used cscript.
c:\x.vbs(2, 7) (null): The specified module could not be found.
2) The version of wscript and cscript is 5.6.0.8825
3) This is latest version because I read that installing the
latest version of scripting host fixes installation problems.
I managed to fix it. I registered scrrun.dll by typing:
regsvr32 c:\windows\system32\scrrun.dll
Thanks for all the help..
--
Comment By: Martin v. Löwis (loewis)
Date: 2004-12-16 14:07
Message:
Logged In: YES
user_id=21627
Can you please try the following things?
1. Run the script
== SNIP
Function CheckDir()
Set FSO = CreateObject("Scripting.FileSystemObject")
if FSO.FolderExists("c:\python24") then
wscript.echo "1"
else
wscript.echo "0"
end if
End Function
CheckDir()
= SNIP ==
in wscript.exe (i.e. save it into c:\x.vbs, then run c:\x.vbs)
2. Report the version of
C:\WINDOWS\SYSTEM32\wscript.exe
(5.6 is too imprecise - could it be that you have 5.6.0.8820?)
3. Install VBScript, from
http://www.microsoft.com/downloads/details.aspx?FamilyId=C717D943
-7E4B-4622-86EB-95A22B832CAA&displaylang=en
--
Comment By: anamh0001 (anamh0001)
Date: 2004-12-16 11:04
Message:
Logged In: YES
user_id=1178107
Please find the msi log file attached.
I managed to pinpoint the area where it breaks.. It's failing
on CheckDir with an error 2896.
-
MSI (c) (88:54) [09:50:38:430]: Doing action: CheckDir
Action start 09:50:38: CheckDir.
MSI (c) (88:3C) [09:50:38:440]: Cloaking enabled.
MSI (c) (88:3C) [09:50:38:440]: Attempting to enable all
disabled priveleges before calling Install on Server
MSI (c) (88:3C) [09:50:38:440]: Connected to service for CA
interface.
MSI (c) (88:88) [09:50:38:580]: Entering
MsiProvideComponentFromDescriptor. Descriptor: 2eAq^]D2g
(8V7Xaq(hoRIngresDBMS>M5KDYSUnf(HA*L[xeX)y, PathBuf:
1C4F348, pcchPathBuf: 1C4F344, pcchArgsOffset: 1C4F2A4
MSI (c) (88:88) [09:50:38:580]:
MsiProvideComponentFromDescriptor called for component
{997FA962-E067-11D1-9396-00A0C90F27F9}: returning
harcoded oleaut32.dll value
MSI (c) (88:88) [09:50:38:580]:
MsiProvideComponentFromDescriptor is returning: 0
Action ended 09:50:38: CheckDir. Return value 3.
MSI (c) (88:54) [09:50:38:921]: Note: 1: 2262 2: Error 3: -
2147287038
DEBUG: Error 2896: Executing action CheckDir failed.
The installer has encountered an unexpected error installing
this package. This may indicate a problem with this package.
The error code is 2896. The arguments are: CheckDir, ,
Action ended 09:50:38: SelectDirectoryDlg. Return value 3.
MSI (c) (88:94) [09:50:38:931]: Doing action: FatalError
Action start 09:50:38: FatalError.
Action 09:50:38: FatalError. Dialog created
Action ended 09:50:39: FatalError. Return value 2.
Action ended 09:50:40: INSTALL. Return value 3.
MSI (c) (88:94) [09:50:40:012]: Destroying RemoteAPI
object.
MSI (c) (88:3C) [09:50:40:012]: Custom Action Manager
thread ending.
--
Comment By: Martin v. Löwis (loewis)
Date: 2004-12-15 23:35
Message:
Logged In: YES
user_id=21627
Can you please run
msiexec /i python-2.4.msi /l*v python.log
and attach the resulting python.log (do NOT paste it into
the SF comment box
[ python-Feature Requests-1085304 ] Make array.array pickle-able
Feature Requests item #1085304, was opened at 2004-12-14 13:50 Message generated for change (Comment added) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1085304&group_id=5470 Category: Python Library Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nicolas Fleury (nidoizo) Assigned to: Raymond Hettinger (rhettinger) Summary: Make array.array pickle-able Initial Comment: Make array.array pickle-able. -- >Comment By: Raymond Hettinger (rhettinger) Date: 2004-12-16 11:28 Message: Logged In: YES user_id=80475 Fixed. See Modules/arraymodule 2.97 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1085304&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1085168 ] Uninstaller unclear about the app it's uninstalling
Bugs item #1085168, was opened at 2004-12-14 10:05 Message generated for change (Settings changed) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085168&group_id=5470 Category: Installation Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Giles Antonio Radford (mewf) >Assigned to: Martin v. Löwis (loewis) Summary: Uninstaller unclear about the app it's uninstalling Initial Comment: The "Uninstall Python" link added to the start mrnu Python 2.4 folder asks "Are you sure you wish to uninstall this product?". This should really ask whether you wish to uninstall Python 2.4 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085168&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1086555 ] refcount problem in syslog
Bugs item #1086555, was opened at 2004-12-16 11:36
Message generated for change (Comment added) made by rhettinger
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086555&group_id=5470
Category: Python Library
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: DSM (dsm001)
Assigned to: Nobody/Anonymous (nobody)
Summary: refcount problem in syslog
Initial Comment:
Refcount problem in syslog.openlog, dating back awhile:
Python 2.5a0 (#10, Dec 15 2004, 19:53:33)
[GCC 3.3.3 (Debian 20040401)] on linux2
Type "help", "copyright", "credits" or "license" for
more information.
>>> import syslog
[25538 refs]
>>> syslog.openlog('a')
[25539 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25575 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25574 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25573 refs]
[etc..]
>>> syslog.openlog(0)
Fatal Python error:
/home/doug/cvsroot/python/dist/src/Modules/syslogmodule.c:62
object at 0x402d75d8 has negative ref count -4
Aborted
ISTM there's a misplaced Py_XDECREF in syslog_openlog.
It's fine as long as no log is open, but after that
each failed PyArg_ParseTuple costs you a ref.
--
>Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-16 11:54
Message:
Logged In: YES
user_id=80475
See if the attached patch solves your problem.
Also, please run the full test suite.
(I'm on Windows and cannot exercise this code.)
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086555&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1086603 ] segfault in readline
Bugs item #1086603, was opened at 2004-12-16 13:02 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=1086603&group_id=5470 Category: Python Library Group: None Status: Open Resolution: None Priority: 5 Submitted By: DSM (dsm001) Assigned to: Nobody/Anonymous (nobody) Summary: segfault in readline Initial Comment: It's possible to produce segfaults using two functions from the readline module by giving them negative values (GNU readline 4.3-10), at least in some circumstances. Python 2.5a0 (#10, Dec 15 2004, 19:53:33) [GCC 3.3.3 (Debian 20040401)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import readline [25290 refs] >>> readline.remove_history_item(-1) Segmentation fault >>> readline.replace_history_item(-1,'abc') Segmentation fault gdb reveals it happens because the (external) remove_history and replace_history_entry don't return NULL in these cases. I'm not sure whether we're responsible for checking the sanity of inputs or the GNU code should be returning NULL and isn't, but at least sometimes it doesn't. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086603&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1085168 ] Uninstaller unclear about the app it's uninstalling
Bugs item #1085168, was opened at 2004-12-14 16:05 Message generated for change (Comment added) made by loewis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085168&group_id=5470 Category: Installation >Group: 3rd Party >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Giles Antonio Radford (mewf) Assigned to: Martin v. Löwis (loewis) Summary: Uninstaller unclear about the app it's uninstalling Initial Comment: The "Uninstall Python" link added to the start mrnu Python 2.4 folder asks "Are you sure you wish to uninstall this product?". This should really ask whether you wish to uninstall Python 2.4 -- >Comment By: Martin v. Löwis (loewis) Date: 2004-12-16 17:48 Message: Logged In: YES user_id=21627 This dialog is directly generated by Installer; the MSI package cannot influence the text displayed. Closing it as a third-party (Microsoft) bug. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085168&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1086555 ] refcount problem in syslog
Bugs item #1086555, was opened at 2004-12-16 11:36
Message generated for change (Comment added) made by dsm001
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086555&group_id=5470
Category: Python Library
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: DSM (dsm001)
Assigned to: Nobody/Anonymous (nobody)
Summary: refcount problem in syslog
Initial Comment:
Refcount problem in syslog.openlog, dating back awhile:
Python 2.5a0 (#10, Dec 15 2004, 19:53:33)
[GCC 3.3.3 (Debian 20040401)] on linux2
Type "help", "copyright", "credits" or "license" for
more information.
>>> import syslog
[25538 refs]
>>> syslog.openlog('a')
[25539 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25575 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25574 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25573 refs]
[etc..]
>>> syslog.openlog(0)
Fatal Python error:
/home/doug/cvsroot/python/dist/src/Modules/syslogmodule.c:62
object at 0x402d75d8 has negative ref count -4
Aborted
ISTM there's a misplaced Py_XDECREF in syslog_openlog.
It's fine as long as no log is open, but after that
each failed PyArg_ParseTuple costs you a ref.
--
>Comment By: DSM (dsm001)
Date: 2004-12-16 13:51
Message:
Logged In: YES
user_id=1175690
Patch works after correcting typo (*new_S_ident_0 should be
*new_S_ident_o); openlog() and closelog() both seem to
refcount as expected; and passes make test without difficulty.
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-16 11:54
Message:
Logged In: YES
user_id=80475
See if the attached patch solves your problem.
Also, please run the full test suite.
(I'm on Windows and cannot exercise this code.)
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086555&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1086642 ] Compile of _socket fails on 2.4
Bugs item #1086642, was opened at 2004-12-16 19:21 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=1086642&group_id=5470 Category: Extension Modules Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: A. Stocker (akosprime) Assigned to: Nobody/Anonymous (nobody) Summary: Compile of _socket fails on 2.4 Initial Comment: I'm attempting to install Python 2.4 on an SGI Origin 2400 running Irix 6.5.22. I'm using gcc (3.3) to compile, and I've tried using three different make programs (make, smake, and gmake[3.80]) but get the same error during compilation during the building of _socket. There was not a problem building 2.2.1 on this machine before, we never built 2.3 so I do not know if the same problem existed. Here is the relevant entry from the make: building '_socket' extension gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -shared -fno-strict-aliasing -I. -I/usr/local/src/Python-2.4/./Include -I/us r/local/include -I/usr/local/src/Python-2.4/Include -I/usr/local/src/Python-2.4 -c /usr/local/src/Python-2.4/Modules/socke tmodule.c -o build/temp.irix64-6.5-2.4/socketmodule.o In file included from /usr/local/src/Python-2.4/Modules/socketmodule.c:280: /usr/local/src/Python-2.4/Modules/addrinfo.h:145:1: warning: "_SS_ALIGNSIZE" redefined In file included from /usr/local/src/Python-2.4/Modules/socketmodule.h:8, from /usr/local/src/Python-2.4/Modules/socketmodule.c:223: /usr/include/sys/socket.h:246:1: warning: this is the location of the previous definition /usr/local/src/Python-2.4/Modules/socketmodule.c: In function `makeipaddr': /usr/local/src/Python-2.4/Modules/socketmodule.c:853: warning: implicit declaration of function `getnameinfo' /usr/local/src/Python-2.4/Modules/socketmodule.c:854: error: `NI_NUMERICHOST' undeclared (first use in this function) /usr/local/src/Python-2.4/Modules/socketmodule.c:854: error: (Each undeclared identifier is reported only once /usr/local/src/Python-2.4/Modules/socketmodule.c:854: error: for each function it appears in.) /usr/local/src/Python-2.4/Modules/socketmodule.c: In function `socket_gethostbyname_ex': /usr/local/src/Python-2.4/Modules/socketmodule.c:2785: warning: implicit declaration of function `gethostbyname_r' /usr/local/src/Python-2.4/Modules/socketmodule.c:2785: warning: assignment makes pointer from integer without a cast /usr/local/src/Python-2.4/Modules/socketmodule.c: In function `socket_gethostbyaddr': /usr/local/src/Python-2.4/Modules/socketmodule.c:2880: warning: implicit declaration of function `gethostbyaddr_r' /usr/local/src/Python-2.4/Modules/socketmodule.c:2881: warning: assignment makes pointer from integer without a cast building '_ssl' extension -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086642&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1086675 ] optparse docs missing section on Extending
Bugs item #1086675, was opened at 2004-12-16 20:25 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=1086675&group_id=5470 Category: Documentation Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Kent Johnson (kjohnson) Assigned to: Nobody/Anonymous (nobody) Summary: optparse docs missing section on Extending Initial Comment: In Python 2.3 the module docs for optparse include a fifth section, 6.20.5 Extending optparse. This section is no longer present in the docs for Python 2.4. It is still present in the current Optik docs (http://optik.sourceforge.net/doc/1.5/extending.html) so my guess is this is an inadvertent omission. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086675&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1086555 ] refcount problem in syslog
Bugs item #1086555, was opened at 2004-12-16 11:36
Message generated for change (Settings changed) made by rhettinger
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086555&group_id=5470
Category: Python Library
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: DSM (dsm001)
Assigned to: Nobody/Anonymous (nobody)
Summary: refcount problem in syslog
Initial Comment:
Refcount problem in syslog.openlog, dating back awhile:
Python 2.5a0 (#10, Dec 15 2004, 19:53:33)
[GCC 3.3.3 (Debian 20040401)] on linux2
Type "help", "copyright", "credits" or "license" for
more information.
>>> import syslog
[25538 refs]
>>> syslog.openlog('a')
[25539 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25575 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25574 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25573 refs]
[etc..]
>>> syslog.openlog(0)
Fatal Python error:
/home/doug/cvsroot/python/dist/src/Modules/syslogmodule.c:62
object at 0x402d75d8 has negative ref count -4
Aborted
ISTM there's a misplaced Py_XDECREF in syslog_openlog.
It's fine as long as no log is open, but after that
each failed PyArg_ParseTuple costs you a ref.
--
>Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-16 18:52
Message:
Logged In: YES
user_id=80475
Fixed.
See Modules/sysmodule.c 2.20
Thanks for submitting the bug report and testing the patch.
--
Comment By: DSM (dsm001)
Date: 2004-12-16 13:51
Message:
Logged In: YES
user_id=1175690
Patch works after correcting typo (*new_S_ident_0 should be
*new_S_ident_o); openlog() and closelog() both seem to
refcount as expected; and passes make test without difficulty.
--
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-16 11:54
Message:
Logged In: YES
user_id=80475
See if the attached patch solves your problem.
Also, please run the full test suite.
(I'm on Windows and cannot exercise this code.)
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086555&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1071248 ] Documented grammar for List displays incorrect (testlist)
Bugs item #1071248, was opened at 2004-11-22 12:26 Message generated for change (Comment added) made by kermode You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1071248&group_id=5470 Category: Documentation Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Lenard Lindstrom (kermode) Assigned to: Jeremy Hylton (jhylton) Summary: Documented grammar for List displays incorrect (testlist) Initial Comment: In section 5.2.4 of the Python Reference Manual for Pythons 2.4 and 2.3 the definition testlist ::= test ( "," test )* [ "," ] should be testlist ::= test [ ( "," test )+ [ "," ] ] to conform with the definition of testlist_safe in the Grammar definition file. In other words, a trailing comma is not permitted if there is only one test in testlist. -- >Comment By: Lenard Lindstrom (kermode) Date: 2004-12-16 16:00 Message: Logged In: YES user_id=663274 Python 2.4 (#60, Nov 30 2004, 11:49:19) [MSC v.1310 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> [x for x in 1,] File "", line 1 [x for x in 1,] ^ SyntaxError: invalid syntax >>> [x for x in 1,2,] [1, 2] >>> for x in 1,: ... print x ... 1 >>> -- Comment By: engelbert gruber (grubert) Date: 2004-12-15 00:50 Message: Logged In: YES user_id=147070 but >>> testlist = 1, >>> testlist (1,) so testlist = 1 does not produce a list testlist ::= one "," ( another "," )* [and [","]] -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1071248&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1086854 ] "slots" member variable in object.h confuses Qt moc utility
Bugs item #1086854, was opened at 2004-12-17 04:07 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=1086854&group_id=5470 Category: Build Group: Platform-specific Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Friesner (jfriesne) Assigned to: Nobody/Anonymous (nobody) Summary: "slots" member variable in object.h confuses Qt moc utility Initial Comment: This isn't really a Python bug per se, but it's easy to fix so I'm filing a bug report anyway. The problem is with the line PyObject *name, *slots; in the definition of struct _heaptypeobject at line 343 of Include/object.h. I'm embedding Python into my app that uses the TrollTech Qt GUI, and Qt has a preprocessor program named "moc" that looks for certain non-standard keywords. One of these keywords is the word "slots"... so having a member variable named "slots" in Include/object.h confuses moc and causes my app to have a build error. I was able to fix the problem by renaming the "slots" member variable to "xslots" in the Python source, but it would be nicer if it was renamed in the official Python distribution so that the problem doesn't come up for the next guy. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086854&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1085208 ] Installation ends prematurely
Bugs item #1085208, was opened at 2004-12-14 16:18
Message generated for change (Comment added) made by anamh0001
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085208&group_id=5470
Category: Installation
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: anamh0001 (anamh0001)
Assigned to: Nobody/Anonymous (nobody)
Summary: Installation ends prematurely
Initial Comment:
Test machine:
Pentium 4M 1.7Ghz
Win XP Pro w/ SP2
512Mb RAM
30Gb HD
.Net Framework 1.0 and 1.1
Windows Scripting Host 5.6
After double clicking the installation file. It proceeds to
act like any other Windows Installer. After accepting
c:\Python24 as the install directory, I am presented with
this screen saying that there was an error and that the
installation has ended prematurely.
FYI, I tried to install over Python 2.3 (as in upgrade) but
I got the same error. So I proceeded to uninstall Python
2.3 and other installed libraries. I then restarted the PC
and tried to install Python 2.4 again. This bug is the
symptom of this second try.
Please find the screenshot attached showing the final
screen.
--
>Comment By: anamh0001 (anamh0001)
Date: 2004-12-16 10:04
Message:
Logged In: YES
user_id=1178107
Please find the msi log file attached.
I managed to pinpoint the area where it breaks.. It's failing
on CheckDir with an error 2896.
-
MSI (c) (88:54) [09:50:38:430]: Doing action: CheckDir
Action start 09:50:38: CheckDir.
MSI (c) (88:3C) [09:50:38:440]: Cloaking enabled.
MSI (c) (88:3C) [09:50:38:440]: Attempting to enable all
disabled priveleges before calling Install on Server
MSI (c) (88:3C) [09:50:38:440]: Connected to service for CA
interface.
MSI (c) (88:88) [09:50:38:580]: Entering
MsiProvideComponentFromDescriptor. Descriptor: 2eAq^]D2g
(8V7Xaq(hoRIngresDBMS>M5KDYSUnf(HA*L[xeX)y, PathBuf:
1C4F348, pcchPathBuf: 1C4F344, pcchArgsOffset: 1C4F2A4
MSI (c) (88:88) [09:50:38:580]:
MsiProvideComponentFromDescriptor called for component
{997FA962-E067-11D1-9396-00A0C90F27F9}: returning
harcoded oleaut32.dll value
MSI (c) (88:88) [09:50:38:580]:
MsiProvideComponentFromDescriptor is returning: 0
Action ended 09:50:38: CheckDir. Return value 3.
MSI (c) (88:54) [09:50:38:921]: Note: 1: 2262 2: Error 3: -
2147287038
DEBUG: Error 2896: Executing action CheckDir failed.
The installer has encountered an unexpected error installing
this package. This may indicate a problem with this package.
The error code is 2896. The arguments are: CheckDir, ,
Action ended 09:50:38: SelectDirectoryDlg. Return value 3.
MSI (c) (88:94) [09:50:38:931]: Doing action: FatalError
Action start 09:50:38: FatalError.
Action 09:50:38: FatalError. Dialog created
Action ended 09:50:39: FatalError. Return value 2.
Action ended 09:50:40: INSTALL. Return value 3.
MSI (c) (88:94) [09:50:40:012]: Destroying RemoteAPI
object.
MSI (c) (88:3C) [09:50:40:012]: Custom Action Manager
thread ending.
--
Comment By: Martin v. Löwis (loewis)
Date: 2004-12-15 22:35
Message:
Logged In: YES
user_id=21627
Can you please run
msiexec /i python-2.4.msi /l*v python.log
and attach the resulting python.log (do NOT paste it into
the SF comment box).
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085208&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1085744 ] PySequence_Tuple not as fast as PySequence_List
Bugs item #1085744, was opened at 2004-12-15 07:15 Message generated for change (Comment added) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1085744&group_id=5470 Category: Python Interpreter Core Group: Python 2.5 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nick Coghlan (ncoghlan) Assigned to: Raymond Hettinger (rhettinger) Summary: PySequence_Tuple not as fast as PySequence_List Initial Comment: A little "my code is faster than your code" game on python-list showed up a pathological interaction between itertools.chain and str.join: C:\>python -m timeit -s "data = [map(str, range(x)) for x in range(1000)]; from itertools import chain" "''.join(chain(*data))" 10 loops, best of 3: 1.2 sec per loop ** OUCH!! Some extra experiments show that creating a list from the result of chain is fast, but creating a tuple is horrendously slow: C:\>python -m timeit -s "data = [map(str, range(x)) for x in range(1000)]; from itertools import chain" "''.join(list(chain(*data)))" 10 loops, best of 3: 107 msec per loop C:\>python -m timeit -s "data = [map(str, range(x)) for x in range(1000)]; from itertools import chain" "''.join(tuple(chain(*data)))" 10 loops, best of 3: 1.2 sec per loop Creating the tuple by means of a list is actually faster than creating the tuple directly: C:\>python -m timeit -s "data = [map(str, range(x)) for x in range(1000)]; from itertools import chain" "''.join(tuple(list(chain(*data" 10 loops, best of 3: 146 msec per loop A check with imap suggests the problem may be a more general interaction between PySequence_Fast and iterators which don't have __len__ methods: C:\>python -m timeit -s "data = [y for x in range(1000) for y in map(str, range(x))]; from itertools import imap; val = lambda arg: arg" "''.join(list(imap(val, data)))" 10 loops, best of 3: 310 msec per loop C:\>python -m timeit -s "data = [y for x in range(1000) for y in map(str, range(x))]; from itertools import imap; val = lambda arg: arg" "''.join(imap(val, data))" 10 loops, best of 3: 1.4 sec per loop Looking at the code supports that, too - PySequence_Fast uses PySequence_Tuple, which is great when PyObject_Size gives a nice answer, but can lead to a lot of tuple resizing when it isn't (one resize per 10 items beyond 10 up to 500, then one resize per 100 items beyond 500). 2.4's optimised list extension means that this *really* hurts performance wise. The other aspect is whether or not some of the utilities in itertools could benefit from a __len__ method that returned a sensible answer if their inputs defined __len__ methods, and returned -1 otherwise (this would certainly work well with PySequence_Tuple, but I realise it's a slightly odd behaviour for a __len__ method). -- >Comment By: Raymond Hettinger (rhettinger) Date: 2004-12-16 05:39 Message: Logged In: YES user_id=80475 Loaded the patch. See Objects/abstract.c 2.133 -- Comment By: Raymond Hettinger (rhettinger) Date: 2004-12-15 16:27 Message: Logged In: YES user_id=80475 Attaching a small patch for PySequence_Tuple. Try it out and let me know if you find it to be an improvement. It also adds a bit of error checking that should have been there anyway. -- Comment By: Raymond Hettinger (rhettinger) Date: 2004-12-15 12:14 Message: Logged In: YES user_id=80475 P.S. In your example, you can get an immediate improvement in performance by having Py_SequenceFast use PySequence_List instead of PySequence_Tuple. If you want to work on some Py2.5 optimizations along these lines, look at replacing the somewhat arbitrary over-allocation strategy in PySequence_Tuple. If you're super-motivated, see if you can improve on the algorithm for str.join. Since these are just strategy changes, they will improve some cases at the expense of others. The goal is to find the one that does the best, most of the time; not horribly in worst situations; and makes the fewest demands on memory. -- Comment By: Raymond Hettinger (rhettinger) Date: 2004-12-15 10:04 Message: Logged In: YES user_id=80475 Remain calm ;-) Also, please isolate the issues instead of clumping everything together. And this is likely best handled by email rather than SF (you're asking me to explain all of your timings rather than pointing to a buggy piece of code). The idea (feature request) to make iterators length transparent has already been explored and reached a dead end. I've implemented it already it the few situations where it can work (for example itertools.repeat(obj, n) and dict.iteritems() report their length). Most other situations run into logical inc
[ python-Bugs-1080660 ] thread.error: release unlocked lock on Queue put
Bugs item #1080660, was opened at 2004-12-07 09:48 Message generated for change (Settings changed) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1080660&group_id=5470 Category: Threads Group: Python 2.3 >Status: Closed >Resolution: Later Priority: 5 Submitted By: John Speno (corvus) Assigned to: Nobody/Anonymous (nobody) Summary: thread.error: release unlocked lock on Queue put Initial Comment: System is Python 2.3.3 on Solaris 9. I'm using the classic Python thread model. Main thread puts stuff into a Queue.Queue() and worker threads get stuff out of it and do their thing. On occaision, I get an exception in the main thread when it tries to put something into the Queue. File "/usr/local/bin/poller.py", line 47, in fragnap_it work_queue.put((foo, bar, baz)) File "/usr/local/lib/python2.3/Queue.py", line 106, in put self.fsema.release() thread.error: release unlocked lock This error still happens intermittently, and I haven't been able to reduce it to a simple case. I can alter my applications to do something useful for debugging this problem when it happens, if you can figure out what "something useful" would be. Just let me know. The queue is unbounded, and I'm using blocking get/put. The main thread creates 20 worker threads, and 1 recorder thread. Then it puts upto 1500 items in the Queue.Queue named work_queue. The 20 worker threads take stuff out work_queue, process some using pure python code, or others by using subprocess.py. Results from the workers are put into another Queue.Queue named results_queue. The Recorder thread gets from the results_queue and writes stuff to a MySQL db. I've never seen the error happen when putting into the results_queue, only from the main thread putting into the work_queue. Thread defines in my python config.h are: #define HAVE_PTHREAD_H 1 #define HAVE_PTHREAD_SIGMASK 1 #define HAVE_THREAD_H 1 #define PTHREAD_SYSTEM_SCHED_SUPPORTED 1 #define SIZEOF_PTHREAD_T 4 #define WITH_THREAD 1 And all the thread related python tests (test_thread, test_threading, and test_queue) pass. -- Comment By: John Speno (corvus) Date: 2004-12-10 12:57 Message: Logged In: YES user_id=2138 Given that I can't reproduce it in a simple test, and it happens so rarely in my real applications, I'm okay with notice of it just being in google and here on sf. Maybe someday someone will encounter it again and we can make progress. -- Comment By: Tim Peters (tim_one) Date: 2004-12-10 12:45 Message: Logged In: YES user_id=31435 No, and there are no known bugs in Queue in 2.3.j. If John can't whittle it down to a test case that fails for others, I expect this bug is hopeless. We talked about it on c.l.py, and what he's seeing should be impossible. Presuming it's a Solaris-specific bug. -- Comment By: Raymond Hettinger (rhettinger) Date: 2004-12-10 12:35 Message: Logged In: YES user_id=80475 Tim, was this something you already fixed in Py2.4? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1080660&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1086555 ] refcount problem in syslog
Bugs item #1086555, was opened at 2004-12-16 11:36
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=1086555&group_id=5470
Category: Python Library
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: DSM (dsm001)
Assigned to: Nobody/Anonymous (nobody)
Summary: refcount problem in syslog
Initial Comment:
Refcount problem in syslog.openlog, dating back awhile:
Python 2.5a0 (#10, Dec 15 2004, 19:53:33)
[GCC 3.3.3 (Debian 20040401)] on linux2
Type "help", "copyright", "credits" or "license" for
more information.
>>> import syslog
[25538 refs]
>>> syslog.openlog('a')
[25539 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25575 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25574 refs]
>>> syslog.openlog(0)
Traceback (most recent call last):
File "", line 1, in ?
TypeError: ident string [, logoption [, facility]]
[25573 refs]
[etc..]
>>> syslog.openlog(0)
Fatal Python error:
/home/doug/cvsroot/python/dist/src/Modules/syslogmodule.c:62
object at 0x402d75d8 has negative ref count -4
Aborted
ISTM there's a misplaced Py_XDECREF in syslog_openlog.
It's fine as long as no log is open, but after that
each failed PyArg_ParseTuple costs you a ref.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086555&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1086675 ] optparse docs missing section on Extending
Bugs item #1086675, was opened at 2004-12-16 15:25 Message generated for change (Settings changed) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086675&group_id=5470 Category: Documentation Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Kent Johnson (kjohnson) >Assigned to: Greg Ward (gward) Summary: optparse docs missing section on Extending Initial Comment: In Python 2.3 the module docs for optparse include a fifth section, 6.20.5 Extending optparse. This section is no longer present in the docs for Python 2.4. It is still present in the current Optik docs (http://optik.sourceforge.net/doc/1.5/extending.html) so my guess is this is an inadvertent omission. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1086675&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
