On 10 Apr 2017, at 12:59, Clemens Lang wrote:
> It's up to you, really. pypi2port might be easier, because it auto-generates
> most
> of the boilerplate and is better tested, since most python ports use PyPI.
Ok, I just want to avoid having too much divergence between current
Hi,
- On 9 Apr, 2017, at 18:01, db iams...@gmail.com wrote:
> When writing a python port, what is best practice for one that's on both PyPI
> and GitHub, use pypi2port or portgroups github+python?
It's up to you, really. pypi2port might be easier, because it auto-generates
most
of the
When writing a python port, what is best practice for one that's on both PyPI
and GitHub, use pypi2port or portgroups github+python?