#40347: py26-pyphant: use python PortGroup, merge multiple ports into subports, upgrade to version 1.0b2 ---------------------------+---------------------- Reporter: mojca@… | Owner: rowue@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py26-pyphant | ---------------------------+---------------------- Comment (by alexander.held@…): Replying to [comment:8 mojca@…]:
I didn't want to ask whether you want to drop support for python 2.6. I
wanted to ask whether you have a reason to keep `py26-pyphant` working in MacPorts in addition to the future `py27-pyphant`.
...
But there have been discussions about gradually removing all ports
depending on Python 2.4, 2.5 and 2.6 (unless a port is incompatible with 2.7, but that sounds like something very outdated anyway), it's probably just that nobody took the time to do that.
So my main question was basically whether there is some need for
`py26-pythant` in MacPorts or if `py27-pyphant` would do as well (once you release the next version of `pyphant` of course). The macports site [http://www.macports.org/ports.php?by=name&substr=py26-] still lists about 700 py26-* ports. To be honest, I don't see a reason to get rid of the older python variants if the port's source is still compatible, unless there is really not a single person out there still using python2.6. I have not been following these discussions. Do you have a link so that I can read about the reasons? I think I need more input in order to be able to decide whether we still need the `py26-pyphant` port after the new release.
Btw: for Pyphant we could test MacPorts packaging from any given commit
on GitHub. So you don't need to create a release just to test.
Thank you for the hint. Actually, we tried this already with `sogl` but we did not succeed, since we do not have the setup.py file in the root of the repository and we could not figure out how to configure macports for this case. `Pyphant` also has several setup.py files in one repository for the main package and the toolboxes for historic reasons. Is it possible to specify the location of the setup.py file within the repository? -- Ticket URL: <https://trac.macports.org/ticket/40347#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X