Restructuring Python ports?

[Akira Kitada]

I had a good discussion on this with Bryan at #macports.

I proposed that we should change all python ports (python2[4-6] and
maybe python30) to be built
the way just as python ports in FreeBSD port system to make it a
little lightweight and bring consistency
to python ports of MacPorts, even if it will break existing ports.
Bryan declined this by saying "for 3.0 i'll definitely contact mww;
but for 2.4/2.5 i'm not sure of the breakage that will happen".

So it's going to remain the same: all-in-one python26 port and other
sliced python ports.
No intentional breakages are introduced.

On Thu, Jan 1, 2009 at 2:13 PM, Akira Kitada <akitada at macports.org> wrote:
> Hi Bryan,
>
>> Like python26 does now?  The advantage is of course that it works as some
>> who expect it to work like the system python, or the official one you
>> download from python.org.  The disadvantage is that it is heavier on
>> dependencies, adding the following to what python25 needs: zlib, openssl,
>> sqlite3, db46, gdbm, tcl, tk, and X11 (because of tk).
>
> And it might be convenient to be able to update each dependent port
> independently,
> but I'm not sure we would really want to update each of them that way.
>
> As always, we could probably learn some ideas from our senior project,
> FreeBSD Ports.
> Here is the patch-setup.py from FreeBSD's. [1]
>
>    # This global variable is used to hold the list of modules to be disabled.
>    -disabled_module_list = []
>    +disabled_module_list = ["_bsddb", "_sqlite3", "_tkinter", "gdbm", "mpz"]
>
> To me, it looks moderate and more pragmatic configuration than
> MacPorts's, where it disables:
>
>    # This global variable is used to hold the list of modules to be disabled.
>    -disabled_module_list = []
>    +disabled_module_list =
> ["zlib","_hashlib","_ssl","_bsddb","_sqlite3","_tkinter","bz2","gdbm","readline","_curses","_curses_panel"]
>
>
> (By the way, I must confess I didn't know python26 changed the way how
> it's built *again*.
> I worry it would bring some more confusions to python ports.)
>
> [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/python25/files/patch-setup.py
>
>> If we're not sure just yet which is preferred, do note that I haven't heard
>> anything personally that python26 brings in too many dependencies, nor have
>> any tickets been filed.  Of course 2.6 is still pretty new, and doesn't yet
>> have the module support the older versions do.
>
> I would like to go in the middle.
>
> Regards,
>
>> Bryan
>>
>>
>>>
>>> [1] MacPorts FAQ: Why can't I import foo in Python 2.5?
>>> http://trac.macports.org/wiki/FAQ#WhycantIimportfooinPython2.5
>>>
>>> [2] About FreeBSD Ports
>>> http://www.freebsd.org/ports/
>> _______________________________________________
>> macports-dev mailing list
>> macports-dev at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>>
>