Re: Proposal: Reorganizing Python for Python2 (and fixes for the previous proposal)
On 11 Jan 2001 12:34:14 -0600, Rob Tillotson <[EMAIL PROTECTED]> wrote: > But for purposes of packaging infrastructure, we can't rely on that. Right -- but it does mean each installed version of Python should know what API version it needs, and installed extensions should know what API version they build against. That means we have directories per API version for .so's, and the correct directories are added to the Python versions. > p.s. why the heck does everybody seem to think cc:ing mailing list > postings is a good idea? stop, please! I'm on the mailing list, I > don't need to see it again... You can setup Mail-Followup-To, or X-No-Cc, or something to let us know, you know (Though PMS doesn't support that yet, I do try to compensate by hand...) -- Moshe Zadka <[EMAIL PROTECTED]> This is a signature anti-virus. Please stop the spread of signature viruses!
Re: Bug#82088: Request build against tcl/tk8.3
On Sat, Jan 13, 2001 at 04:41:09AM -0600, Gordon Sadler wrote: > Package: python2-tk > Version: N/A; reported 2001-01-13 > Severity: normal > > I haven't installed these from unstable yet. But I have had python1.52 > and python2 from p.d.o/~flight, both downloaded as source and rebuilt > locally with tcl/tk8.3. > > Now that python2 is coming into unstable, is there any reason we can't > finally update to tcl/tk8.3? It doesn't take much work, change the > Setup file to point to correct lib dir, _tkinter.c, and tkappinit.c . > > Would be very appreciated, it's annoying to keep multiple versions of > libraries around without good cause. I'm all open for this, but I don't know what is best. Python 1.5.2 currently is built with Tcl/Tk8.0, since back in June I was told by both Fredrik Lundh (Tkinter) as well as our Tk maintainer David Engel, that using 8.0 would be the safest bet. Now I just saw that, starting with Python 1.6, Misc/NEWS says that we're now prepared for Tcl/Tk 8.2 and 8.3; I hadn't noticed that before. What makes me a little bit unsure is that Tcl/Tk8.3 isn't yet in testing, but only in unstable. This means that python2 will sit in unstable until tk8.3 moves to testing. Also, the vast majority of packages using Tk in sid still depend on tk8.0 (60 packages), compared to tk8.2 (19 packages) and tk8.3 (18 packages). Anyway, I guess I'll build the next package revision with Tcl/Tk8.3. I'm also working on backporting Tkinter from Python 1.6a2 to the python-tk package in order to make the transition complete (and in order to resolve me from the task of installing/deinstalling the correct tk8.x-dev packages each time I'm building python or python2 ;-). Or does somebody think it's worthwhile to provide python2-tk8.x packages ? Since the tk8.0-dev and tk8.3-dev still seem to conflict, the building of the packages would be the biggest problem. Gregor
Re: Bug#82088: Request build against tcl/tk8.3
[Cc list trimmed a bit; my apologies if you're getting copies and don't want to] On Sat, Jan 13, 2001 at 08:56:19PM +0100, Gregor Hoffleit <[EMAIL PROTECTED]> spake forth: > Anyway, I guess I'll build the next package revision with Tcl/Tk8.3. I'm > also working on backporting Tkinter from Python 1.6a2 to the python-tk > package in order to make the transition complete (and in order to resolve me > from the task of installing/deinstalling the correct tk8.x-dev packages each > time I'm building python or python2 ;-). You may want to hold off on that for a few days while I work out the strange bug that's preventing tcl8.3 from building only on m68k. That bug is the principal reason that tcl8.3 and tk8.3 aren't yet in testing, but Roman has promised an account on kullervo to try to figure it out. > Or does somebody think it's worthwhile to provide python2-tk8.x packages ? > Since the tk8.0-dev and tk8.3-dev still seem to conflict, the building of > the packages would be the biggest problem. Yes, you'd need separate source packages I think... -- Mike Markley <[EMAIL PROTECTED]> GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084 Another war ... must it always be so? How many comrades have we lost in this way? ... Obedience. Duty. Death, and more death ... - Romulan Commander, "Balance of Terror", stardate 1709.2
Re: Proposal: Reorganizing Python for Python 2.0
On Wed, Jan 10, 2001 at 12:32:02PM -0800, Neil Schemenauer wrote: > On Wed, Jan 10, 2001 at 11:01:40PM +0100, [EMAIL PROTECTED] wrote: > I've already built a Python 2.0 package with installs along side > of the regular Debian Python package. Someone asked for them so here they are: http://people.debian.org/~nas/ The packages are a little rough but they work for me. YMMV. Neil
