Opened 15 years ago

Closed 9 years ago

#22407 closed enhancement (wontfix)

Python interpreter build inconsistency across versions

Reported by: akitada@… Owned by: petrrr
Priority: Normal Milestone:
Component: ports Version: 1.8.1
Keywords: python Cc: jaroel (Roel Bruggink), jyrkiwahlstedt, blb@…, MarcusCalhoun-Lopez (Marcus Calhoun-Lopez), erickt@…
Port: python24, python25, python26, python31

Description

For example, python26 is framework build but python25 is not. Can we change this inconsistency to get it simpler?

Change History (9)

comment:1 Changed 15 years ago by blb@…

2.5 is partly a framework build, and technically should be more like 2.6; however, making that change would require some severe pain for all people who have it and ports depending on it currently installed.

2.6+ should be like 2.6 is (2.5's method of framework build causes a symlink issue, if you search for "not a directory" during activation, that's the problem) and we really should be pushing everything away from < 2.6 at this point. I've moved some ports that way, but there are still more. Once done then hopefully all the py- and py25- ports can simply be removed.

comment:2 Changed 15 years ago by jmroot (Joshua Root)

Cc: jwa@… added; mww@… removed

comment:3 Changed 15 years ago by jmroot (Joshua Root)

Cc: roel@… added

comment:4 Changed 11 years ago by petrrr

Cc: Peter.Danecek@… added

Cc Me!

comment:5 Changed 10 years ago by petrrr

Python 2.4 and 2.5 (as well as 3.1) will be gone soon. I guess, we can close this ticket as wontfix. Any objections?

comment:6 Changed 10 years ago by petrrr

Cc: Peter.Danecek@… removed
Owner: changed from macports-tickets@… to petr@…
Status: newassigned

comment:7 Changed 10 years ago by jaroel (Roel Bruggink)

No objections.

comment:8 Changed 10 years ago by jmroot (Joshua Root)

I would call it fixed when they are deleted. Sounds more positive. :)

comment:9 Changed 9 years ago by petrrr

Resolution: wontfix
Status: assignedclosed

The old Python versions are still around (probably they could be removed by now), but I guess no one has intention to fix this anymore.

Note: See TracTickets for help on using tickets.