py-ipy update to 0.82a, add Python 3.4 support

[eirnym (Eir Nym)]

Update py-ipy to 0.82a and which adds Python 3.4 support

[mf2k (Frank Schima)]

Only py34 should be added. The other versions are obsolete and support for them is being removed.

[petrrr]

Cc Me!

[eirnym (Eir Nym)]

IPy has been upgraded to 0.83

[petrrr]

Would you mind to provide a new diff?

[eirnym (Eir Nym)]

update to 0.83

[eirnym (Eir Nym)]

Replying to petr@…:

Would you mind to provide a new diff?.

I have given up before because most MacPorts maintainers I collaborate here are used to reply after long period than post came up. In FreeBSD this time is 10 days at most and 1 month if maintainer is not showed up. So it is cheaper to update your VirtualEnv in most times than ask maintainers to update software.

Also there is live checker for new versions for MacPorts, and it can has system to automatically create such bug reports such this.

PS: I'm sorry to saying this, but it's true. I've came to maintain my own macports repository, which I can put on GitHub/BitBucket and open pull requests to everyone who want.

[eirnym (Eir Nym)]

Replying to petr@…:

Would you mind to provide a new diff?

I've updated diff

[petrrr]

Thanks! But in future please provide the diff against the version available in the repository, otherwise it cannot be applied immediately. It is also helpful when the feedback provided by reviewers is incorporated (subports!).

I now did the edits and committed in r139751 (with r139753 adding a missing py-graveyard edit).

Apart from the update, this implements:

• retire py26 subport
• add py34 subport
• remove unnecessary default version
• correction to livecheck
• set noarch
• minor related changes and format

You can provide an new diff if any of this is not okay.

[eirnym (Eir Nym)]

Replying to petr@…:

Thanks! But in future please provide the diff against the version available in the repository, otherwise it cannot be applied immediately. It is also helpful when the feedback provided by reviewers is incorporated (subports!).

Patch has been provided 5 months ago, and nothing happened after. I've posted notification about 0.83 update in hope that someone find forgotten ticket. And you've asked patch after 6 weeks after last update. I understand. I maintain own MacPorts tree for patches not applied to, but necessary for me in MacPorts Almost all packages for Python/Ruby/Perl I install in their virtual environments, because I'll spend much more time in "patching" MacPorts rather than update it for my project. I think this is reason why most of developers create formulas for homebrew, but not for MacPorts.

I now did the edits and committed in r139751 (with r139753 adding a missing py-graveyard edit).

Apart from the update, this implements:

• retire py26 subport
• add py34 subport
• remove unnecessary default version
• correction to livecheck
• set noarch
• minor related changes and format

You can provide an new diff if any of this is not okay.

I will not provide new patch for this port because I'm NOT a maintainer.

[petrrr]

This is not the appropriate place to discuss the differences of MacPorts vs. Homebrew here. But you can find a couple of discussions for example in the mail list archives.

In any case both projects depend on the voluntary contributions their user community.

The delay is probably due to a non responsive maintainer. There is actually an open Port abandoned ticket (but you could to this as well if you feel that a maintainer retired). You can even propose yourself as maintainer if you are interested.