python25 drops modules by default, but python24 doesn't

[ebgssth@…]

Python2.5 disables common modules by default, but python2.4 doesn't. See dports/lang/python25/files/patch-setup.py

 # 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"]

IMHO, all python pors should be as similar as they can be.

[ebgssth@…]

If there's a reason, please make it clear by leaving comments about that on the patch file.

[raimue@…]

These are provided as seperate ports. For example py25-hashlib, py25-zlib and others. I don't know what the advantage of that was, but we already had that discussion once.

Portfile writers should include correct dependencies.

[ebgssth@…]

I think that's OK, but the thing is python24 doesn't drop these modules. It's a weird...

[raimue@…]

If we were going to change this, it would require to change dependencies in nearly all py-* ports.

[ebgssth@…]

Replying to raimue@macports.org:

If we were going to change this, it would require to change dependencies in nearly all py-* ports.

Yes, we probably have to check py-ports that was not in py25 ports

$ port list |egrep -i '^py-'       | cut -d" " -f1                                      | sort -u > py24
$ port list |egrep -i '^py25-'  | cut -d" " -f1 |  sed 's/^py25/py/' | sort -u > py25
$ wc -l py2[45]
     338 py24
     109 py25
     447 total
$ comm -2 -3 py24 py25 > py24-only
$ wc -l py24-only
     259 py24-only

How about create py25- ports of all 259 py24 only ports? To create py25-ports, we need to know the port need zlib or hashlib, which helps identify this py24 ports should be fixed.

[ebgssth@…]

From a different point of view, that MacPorts has lots more python2.4 ports than python2.5's seems weird to me. (Python 2.5 is the current stable, Python 2.4 series will be no longer released anymore)

Should I open another ticket about this problem?

[raimue@…]

Replying to ebgssth@gmail.com:

Yes, we probably have to check py-ports that was not in py25 ports

No, py25-foo can have different dependencies than py-foo. I don't know what you wanted to tell us with this.

And there is no problem that we have more py-* ports than py25-* ports. We just add what people request. If nobody needs a port, but it is in the tree, it is just more work for maintainers. So if you need some port, ask for it.

PS: This kind of discussion would have been better on the mailing list.

[akira@…]

Now that python 2.6 is released, I think it isn't worth working on this issue. Closing.