Opened 13 years ago
Closed 12 years ago
#29978 closed submission (fixed)
New port: py27-iniparse (Python package for modifying ini files)
Reported by: | marc.schlaich@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | jonny.dee@… | |
Port: | py27-iniparse |
Description
Attachments (1)
Change History (7)
Changed 13 years ago by marc.schlaich@…
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 13 years ago by marc.schlaich@…
There are the following changes:
- I fixed the download location because the old link does not work.
- I stripped the short description because IMO it was to long, I can undo this if you want to.
- I check if distribute is necessary
I await your answer to point 2 and submit a new Portfile.
comment:3 Changed 13 years ago by jonny.dee@…
I just would like to mention that it's 8 months later now and nothing has happened. Would it be possible to finish whatever needs to be done and release 'py27-iniparse'? Thank you very much and best regards, Jonny
comment:5 Changed 13 years ago by mf2k (Frank Schima)
The py*-iniparse ports should be merged using the unified python 1.0 portgroup with subgroups to add py27.
comment:6 Changed 12 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Why is this py27-iniparse portfile so drastically different from the existing portfile for py26-iniparse? I would prefer to see a py27-iniparse portfile based on the py26-iniparse portfile. If you believe there are errors in the existing py26-iniparse portfile (for example, does it need a dependency on distribute?) then submit a ticket with those changes to py26-iniparse (and py25-iniparse and py-iniparse) first.