Quantcast

python port - use pypi or github

classic Classic list List threaded Threaded
3 messages Options
db
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

python port - use pypi or github

db
When writing a python port, what is best practice for one that's on both PyPI and GitHub, use pypi2port or portgroups github+python?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: python port - use pypi or github

Clemens Lang-2
Hi,

----- On 9 Apr, 2017, at 18:01, db [hidden email] 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 boilerplate and is better tested, since most python ports use PyPI.


HTH,
--
Clemens Lang
db
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: python port - use pypi or github

db
On 10 Apr 2017, at 12:59, Clemens Lang <[hidden email]> 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 development, releases and packages. I don't know if that happens often with ports.
Loading...