[ python-Bugs-1230161 ] Build failure
Bugs item #1230161, was opened at 2005-06-30 06:27 Message generated for change (Settings changed) made by ceramond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1230161&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build Group: Python 2.4 >Status: Closed Resolution: None Priority: 5 Submitted By: L.M (ceramond) Assigned to: Nobody/Anonymous (nobody) Summary: Build failure Initial Comment: ./configure + make fails with various errors on FreeBSD 4.11-RELEASE case $MAKEFLAGS in *-s*) CC='gcc -pthread' LDSHARED='gcc -shared' OPT='-DNDEBUG -g -O3 -Wall -Wstrict-prototypes' ./python -E ./setup.py -q build;; *) CC='gcc -pthread' LDSHARED='gcc -shared' OPT='-DNDEBUG -g -O3 -Wall -Wstrict-prototypes' ./python -E ./setup.py build;; esac Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] 'import site' failed; use -v for traceback Traceback (most recent call last): File "./setup.py", line 6, in ? import sys, os, getopt, imp, re ImportError: No module named os *** Error code 1 If I run "make" again, it stops with this, instead, I found it strange because "pwd.so" isn't ready yet. case $MAKEFLAGS in *-s*) CC='gcc -pthread' LDSHARED='gcc -shared' OPT='-DNDEBUG -g -O3 -Wall -Wstrict-prototypes' ./python -E ./setup.py -q build;; *) CC='gcc -pthread' LDSHARED='gcc -shared' OPT='-DNDEBUG -g -O3 -Wall -Wstrict-prototypes' ./python -E ./setup.py build;; esac Traceback (most recent call last): File "./setup.py", line 1184, in ? main() File "./setup.py", line 1178, in main scripts = ['Tools/scripts/pydoc', 'Tools/scripts/idle', File "/home/mondo/Python-2.4.1/Lib/distutils/core.py", line 123, in setup dist.parse_config_files() File "/home/mondo/Python-2.4.1/Lib/distutils/dist.py", line 339, in parse_config_files filenames = self.find_config_files() File "/home/mondo/Python-2.4.1/Lib/distutils/dist.py", line 302, in find_config_files check_environ() File "/home/mondo/Python-2.4.1/Lib/distutils/util.py", line 155, in check_environ import pwd ImportError: No module named pwd *** Error code 1 I've tried "make clean" + retry, giving --prefix=so-and-so to ./configure, and some other things without success. I have already built exactly same Python source on this server several weeks ago (in a different directory), and do not understand why it's failing, now. (Possibly, admin updated something causing build process to fail...) -- >Comment By: L.M (ceramond) Date: 2005-07-06 14:13 Message: Logged In: YES user_id=1305168 Thank you for the info. "export HOME" soplved the problem. HOME wasn't exported because I was compiling on shared hosting environment, and the host doesn't set normal env variables. I set HOME (and some other env var), but didn't export them. And that caused the build failure. -- Comment By: Martin v. Löwis (loewis) Date: 2005-07-06 05:20 Message: Logged In: YES user_id=21627 The pwd module is only used if HOME isn't set. Why is HOME not set on your system? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1230161&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1233578 ] Pickle protocols 1, 2 can't handle "inf" floats.
Bugs item #1233578, was opened at 2005-07-06 10:03
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=1233578&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Charles (melicertes)
Assigned to: Nobody/Anonymous (nobody)
Summary: Pickle protocols 1, 2 can't handle "inf" floats.
Initial Comment:
Python 2.4.1 on an AMD64 system. The pickle module
barfs with a "SystemError: frexp() result out of range"
if an "inf" float value is pickled with pickle protocol
1 or 2. It works fine with the old protocol 0.
Minimal test case:
>>> import pickle
>>> o = 2e308
>>> print o
inf
>>> pickle.dumps(o, protocol=0)
'Finf\n.'
>>>
>>> pickle.dumps(o, protocol=1)
Traceback (most recent call last):
File "", line 1, in ?
File "/usr/lib/python2.4/pickle.py", line 1386, in dumps
Pickler(file, protocol, bin).dump(obj)
File "/usr/lib/python2.4/pickle.py", line 231, in dump
self.save(obj)
File "/usr/lib/python2.4/pickle.py", line 293, in save
f(self, obj) # Call unbound method with explicit self
File "/usr/lib/python2.4/pickle.py", line 489, in
save_float
self.write(BINFLOAT + pack('>d', obj))
SystemError: frexp() result out of range
>>>
>>> pickle.dumps(o, protocol=2)
Traceback (most recent call last):
File "", line 1, in ?
File "/usr/lib/python2.4/pickle.py", line 1386, in dumps
Pickler(file, protocol, bin).dump(obj)
File "/usr/lib/python2.4/pickle.py", line 231, in dump
self.save(obj)
File "/usr/lib/python2.4/pickle.py", line 293, in save
f(self, obj) # Call unbound method with explicit self
File "/usr/lib/python2.4/pickle.py", line 489, in
save_float
self.write(BINFLOAT + pack('>d', obj))
SystemError: frexp() result out of range
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1233578&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1233578 ] Pickle protocols 1, 2 can't handle "inf" floats.
Bugs item #1233578, was opened at 2005-07-06 17:03
Message generated for change (Comment added) made by mwh
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1233578&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.4
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Charles (melicertes)
>Assigned to: Michael Hudson (mwh)
Summary: Pickle protocols 1, 2 can't handle "inf" floats.
Initial Comment:
Python 2.4.1 on an AMD64 system. The pickle module
barfs with a "SystemError: frexp() result out of range"
if an "inf" float value is pickled with pickle protocol
1 or 2. It works fine with the old protocol 0.
Minimal test case:
>>> import pickle
>>> o = 2e308
>>> print o
inf
>>> pickle.dumps(o, protocol=0)
'Finf\n.'
>>>
>>> pickle.dumps(o, protocol=1)
Traceback (most recent call last):
File "", line 1, in ?
File "/usr/lib/python2.4/pickle.py", line 1386, in dumps
Pickler(file, protocol, bin).dump(obj)
File "/usr/lib/python2.4/pickle.py", line 231, in dump
self.save(obj)
File "/usr/lib/python2.4/pickle.py", line 293, in save
f(self, obj) # Call unbound method with explicit self
File "/usr/lib/python2.4/pickle.py", line 489, in
save_float
self.write(BINFLOAT + pack('>d', obj))
SystemError: frexp() result out of range
>>>
>>> pickle.dumps(o, protocol=2)
Traceback (most recent call last):
File "", line 1, in ?
File "/usr/lib/python2.4/pickle.py", line 1386, in dumps
Pickler(file, protocol, bin).dump(obj)
File "/usr/lib/python2.4/pickle.py", line 231, in dump
self.save(obj)
File "/usr/lib/python2.4/pickle.py", line 293, in save
f(self, obj) # Call unbound method with explicit self
File "/usr/lib/python2.4/pickle.py", line 489, in
save_float
self.write(BINFLOAT + pack('>d', obj))
SystemError: frexp() result out of range
--
>Comment By: Michael Hudson (mwh)
Date: 2005-07-06 17:06
Message:
Logged In: YES
user_id=6656
This is fixed in CVS.
(And also the third time I've closed this bug in the last
fortnight! FFS guys!)
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1233578&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1233049 ] openssl-0.9.8 requires _ssl.mak change
Bugs item #1233049, was opened at 2005-07-05 22:14 Message generated for change (Comment added) made by vrmeyer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1233049&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build Group: 3rd Party Status: Closed Resolution: Invalid Priority: 5 Submitted By: Alan Meyer (vrmeyer) Assigned to: Nobody/Anonymous (nobody) Summary: openssl-0.9.8 requires _ssl.mak change Initial Comment: When building _ssl.pyd for Windows I downloaded the latest openssl (0.9.8) released today, July 5, 2005. After building the openssl libraries successfully I downloaded the source code for Python 2.4.1 and ran PCBuild/_ssl.mak. It failed to link four Windows functions in cryptlib.obj in libeay32.lib in openssl. To fix this, "user32.lib" must be added to the definition of "LIBS" in _ssl.mak. We have not tested further, deciding to fallback to an earlier version of openssl since, clearly this latest version had not yet been tested with Python and we are building this for production code. -- >Comment By: Alan Meyer (vrmeyer) Date: 2005-07-06 17:02 Message: Logged In: YES user_id=338015 I agree it's not a bug but didn't see any way to indicate it as an enhancement in the SourceForge interface. I recorded it simply as a note to whoever supports ssl in Python since they will eventually want to upgrade to later versions of openssl, and thought my note might save them a bit of trouble. Thanks for your support of Python. Regards, Alan -- Comment By: Martin v. Löwis (loewis) Date: 2005-07-06 05:14 Message: Logged In: YES user_id=21627 This is indeed not a bug. The build process on Windows is only meant to work with the versions of packages listed in PCbuild/readme.txt, which means OpenSSL 0.9.7d. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1233049&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1233049 ] openssl-0.9.8 requires _ssl.mak change
Bugs item #1233049, was opened at 2005-07-06 00:14 Message generated for change (Comment added) made by loewis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1233049&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build Group: 3rd Party Status: Closed Resolution: Invalid Priority: 5 Submitted By: Alan Meyer (vrmeyer) Assigned to: Nobody/Anonymous (nobody) Summary: openssl-0.9.8 requires _ssl.mak change Initial Comment: When building _ssl.pyd for Windows I downloaded the latest openssl (0.9.8) released today, July 5, 2005. After building the openssl libraries successfully I downloaded the source code for Python 2.4.1 and ran PCBuild/_ssl.mak. It failed to link four Windows functions in cryptlib.obj in libeay32.lib in openssl. To fix this, "user32.lib" must be added to the definition of "LIBS" in _ssl.mak. We have not tested further, deciding to fallback to an earlier version of openssl since, clearly this latest version had not yet been tested with Python and we are building this for production code. -- >Comment By: Martin v. Löwis (loewis) Date: 2005-07-06 21:34 Message: Logged In: YES user_id=21627 Thanks, I have added a remark into readme.txt 1.59. -- Comment By: Alan Meyer (vrmeyer) Date: 2005-07-06 19:02 Message: Logged In: YES user_id=338015 I agree it's not a bug but didn't see any way to indicate it as an enhancement in the SourceForge interface. I recorded it simply as a note to whoever supports ssl in Python since they will eventually want to upgrade to later versions of openssl, and thought my note might save them a bit of trouble. Thanks for your support of Python. Regards, Alan -- Comment By: Martin v. Löwis (loewis) Date: 2005-07-06 07:14 Message: Logged In: YES user_id=21627 This is indeed not a bug. The build process on Windows is only meant to work with the versions of packages listed in PCbuild/readme.txt, which means OpenSSL 0.9.7d. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1233049&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1233785 ] getpass.getpass() performs differently on Windows vs *nix
Bugs item #1233785, was opened at 2005-07-07 09: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=1233785&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Darryl Dixon (esrever_otua) Assigned to: Nobody/Anonymous (nobody) Summary: getpass.getpass() performs differently on Windows vs *nix Initial Comment: getpass.getpass() on *nix platforms allows users to input unicode characters and other NLS input. getpass.getpass() on Windows only allows ASCII input in the 0-127 codepage range. This means that getpass can not be used cross-platform for complex passwords. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1233785&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1233799 ] tkFileDialog.askopen... fails when dir=""
Bugs item #1233799, was opened at 2005-07-06 15:08 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=1233799&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Tkinter Group: Python 2.3 Status: Open Resolution: None Priority: 5 Submitted By: Russell Owen (reowen) Assigned to: Martin v. Löwis (loewis) Summary: tkFileDialog.askopen... fails when dir="" Initial Comment: The following simple code fails on MacOS X 10.3 running the built- in python 2.3 and Aqua Tcl/Tk 8.4.9: import Tkinter import tkFileDialog root = Tkinter.Tk() newPath = tkFileDialog.askopenfilename( initialdir = "", ) The error is: Traceback (most recent call last): File "tkFileDialog_askopen bug.py", line 5, in ? newPath = tkFileDialog.askopenfilename( File "/System/Library/Frameworks/Python.framework/Versions/2.3/ lib/python2.3/lib-tk/tkFileDialog.py", line 119, in askopenfilename return Open(**options).show() File "/System/Library/Frameworks/Python.framework/Versions/2.3/ lib/python2.3/lib-tk/tkCommonDialog.py", line 52, in show s = w.tk.call(self.command, *w._options(self.options)) _tkinter.TclError: bad directory "" The same code runs fine on unix Python 2.2.3 with unknown tcl/tk and on and unix Python 2.4.1 with tcl/tk 8.4.9. it starts out in the user's home directory as I'd expect. Mind you, I know I can use None or not specify the initialdir argument. But in my code it's a string that *might* be empty. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1233799&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
