Path: csiph.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!news.dns-netz.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod
From: Fioddor Superconcentrado <fioddor@gmail.com>
Newsgroups: linux.debian.maint.python
Subject: Re: How to watch pypi.org
Date: Fri, 30 Oct 2020 15:20:02 +0100
Message-ID: <B5Dq2-3F1-5@gated-at.bofh.it>
References: <AWe7v-7OL-5@gated-at.bofh.it> <AWoqe-65e-9@gated-at.bofh.it>
Old-Return-Path: <fioddor@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0000000000007e89d105b2e41425"
Approved: robomod@news.nic.it
Lines: 66
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:12985

--0000000000007e89d105b2e41425
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

As I said I'm very new to this and all (python) packages I'm using lately
use the usual python tools (pipy, setup.py, etc) and my first approach has
been to stick as close as possible to the upstream procedures. But I might
very likely be taking a wrong decision. What are the reasons to go for git
instead of pypi? I see that it is 'more upstream' but it seems that
everyone else is pointing to pypi as a distro-agnostic solution.

El lun., 5 oct. 2020 a las 4:24, Paul Wise (<pabs@debian.org>) escribi=C3=
=B3:

> On Sun, Oct 4, 2020 at 3:29 PM Fioddor Superconcentrado wrote:
>
> > I've packaged a project provided via https://pipi.org and I wanted to
> create a debian/watch file but pipi.org publishes the tarball behind a
> strange url like
>
> I would suggest using the upstream git repo instead of the PyPi tarballs.
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
>
>

--0000000000007e89d105b2e41425
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>As I said I&#39;m very new to this and all (python) p=
ackages I&#39;m using lately use the usual python tools (pipy, setup.py, et=
c) and my first approach has been to stick as close as possible to the upst=
ream procedures. But I might very likely be taking a wrong decision. What a=
re the reasons to go for git instead of pypi? I see that it is &#39;more up=
stream&#39; but it seems that everyone else is pointing to pypi as a distro=
-agnostic solution.<br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">El lun., 5 oct. 2020 a las 4:24, Paul Wise (&=
lt;<a href=3D"mailto:pabs@debian.org">pabs@debian.org</a>&gt;) escribi=C3=
=B3:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sun, Oct=
 4, 2020 at 3:29 PM Fioddor Superconcentrado wrote:<br>
<br>
&gt; I&#39;ve packaged a project provided via <a href=3D"https://pipi.org" =
rel=3D"noreferrer" target=3D"_blank">https://pipi.org</a> and I wanted to c=
reate a debian/watch file but <a href=3D"http://pipi.org" rel=3D"noreferrer=
" target=3D"_blank">pipi.org</a> publishes the tarball behind a strange url=
 like<br>
<br>
I would suggest using the upstream git repo instead of the PyPi tarballs.<b=
r>
<br>
-- <br>
bye,<br>
pabs<br>
<br>
<a href=3D"https://wiki.debian.org/PaulWise" rel=3D"noreferrer" target=3D"_=
blank">https://wiki.debian.org/PaulWise</a><br>
<br>
</blockquote></div>

--0000000000007e89d105b2e41425--