On Oct 21, 2006, at 8:03 PM, [EMAIL PROTECTED] wrote:
Followup #2...
Yesterday I whittled my problems with test_sqlite on my OSX g5 to
test_ctypes and test_sqlite:
./python.exe Lib/test/regrtest.py -l -f tests
test_ctypes
test_sqlite
test test_sqlite failed -- errors occurred;
Patch http://www.python.org/sf/1580674 fixes readlink's behaviour
w.r.t. Unicode strings: without this patch this function uses the
system default encoding instead of the filesystem encoding to convert
Unicode objects to plain strings. Like os.listdir, os.readlink will
now return a Unicode
Ronald Oussoren wrote:
> Patch http://www.python.org/sf/1580674 fixes readlink's behaviour w.r.t.
> Unicode strings: without this patch this function uses the system
> default encoding instead of the filesystem encoding to convert Unicode
> objects to plain strings. Like os.listdir, os.readlink wil
On Oct 22, 2006, at 12:54 PM, Ronald Oussoren wrote a message with an
annoyingly large subject...
Sorry about that, I guess it's time to book a course on basic
computer usage :-(
Ronald
smime.p7s
Description: S/MIME cryptographic signature
__
Ronald> According to a comment in (IIRC) the pyOpenGL sources GLUT on
Ronald> OSX does a chdir() during initialization, that could be the
Ronald> problem here.
How would that explain that it fails on my g5 but not on my powerbook? They
are at the same revision of the operating system
Forgot to send this to python-dev. =)-- Forwarded message --From: Brett Cannon <[EMAIL PROTECTED]
>Date: Oct 20, 2006 1:35 PMSubject: PSF Infrastructure has chosen Roundup as the issue tracker for Python developmentTo: python-list@python.orgAt the beginning of the month the PSF Inf
On Sun, 22 Oct 2006 07:51:27 -0500, [EMAIL PROTECTED] wrote:
>
>Ronald> According to a comment in (IIRC) the pyOpenGL sources GLUT on
>Ronald> OSX does a chdir() during initialization, that could be the
>Ronald> problem here.
>
>How would that explain that it fails on my g5 but not on m
Thanks to the folks involved in this prcocess - I'm looking forward to getting
the hell away from SF's bug tracker. :-)
Anthony
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mai
Anthony Baxter wrote:
> Thanks to the folks involved in this prcocess - I'm looking forward to
> getting
> the hell away from SF's bug tracker. :-)
Yes, let us know when the new tracker is up, I want to start using it :)
___
Python-Dev mailing list
Py
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 22, 2006, at 8:51 AM, [EMAIL PROTECTED] wrote:
> Is there anyone else with a g5 who can do a vanilla Unix (not
> framework)
> build on an up-to-date g5 from an up-to-date Subversion
> repository? It
> would be nice if someone else could at
Barry> What do you get when you check _sqlite3?
$ otool -L ./build/lib.mac-10.3-ppc-2.6/_sqlite3.so
./build/lib.macosx-10.3-ppc-2.6/_sqlite3.so:
/usr/local/lib/libsqlite3.0.dylib (compatibility version 9.0.0,
current version 9.6.0)
/usr/lib/libmx.A.dylib (comp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 22, 2006, at 11:24 PM, [EMAIL PROTECTED] wrote:
> According to /usr/include/sqlite3.h, what's installed by Apple is
> 3.1.3.
> Aside from the possibility that I somehow compiled against
> /usr/include/sqlite3.h and linked against /usr/local/l
Martin v. Löwis wrote:
> It's not clear to me what you want to achieve with these patches,
> in particular, whether you want to see them integrated into Python or
> not.
>
I would be thrilled if they were, but it seems less likely with every
passing day. If you have some advice on how I might
Larry Hastings wrote:
> Martin v. Löwis wrote:
> Let's be specific: when there is at least one long-lived small lazy
> slice of a large string, and the large string itself would otherwise
> have been dereferenced and freed, and this small slice is never examined
> by code outside of stringobjec
Larry Hastings schrieb:
> Anyway, it was my intent to post the patch and see what happened. Being
> a first-timer at this, and not having even read the core development
> mailing lists for very long, I had no idea what to expect. Though I
> genuinely didn't expect it to be this brusque.
I cou
Larry Hastings <[EMAIL PROTECTED]> wrote:
> It was/is my understanding that the early days of a new major revision
> was the most judicious time to introduce big changes. If I had offered
> these patches six months ago for 2.5, they would have had zero chance of
> acceptance. But 2.6 is in it
Josiah Carlson wrote:
> It would be a radical change for Python 2.6, and really the 2.x series,
> likely requiring nontrivial changes to extension modules that deal with
> strings, and the assumptions about strings that have held for over a
> decade.
the assumptions hidden in everyone's use of th
17 matches
Mail list logo
