[Buildroot] [PATCH] python-can: bump to 1.4.1

Yegor Yefremov yegorslists at googlemail.com
Mon Jan 4 08:54:46 UTC 2016


Arnout, All

On Sun, Jan 3, 2016 at 11:24 PM, Arnout Vandecappelle <arnout at mind.be> wrote:
> On 02-01-16 22:50, Angelo Compagnucci wrote:
>> Yegor, Arnout, All
>>
>> 2016-01-02 22:04 GMT+01:00 Arnout Vandecappelle <arnout at mind.be>:
>>> > On 02-01-16 12:15, Yann E. MORIN wrote:
>>>> >> Yegor, All,
>>>> >>
>>> >
>>> > [snip]
>>> >
>>>> >> Still, I think we should use upstream locations, not some packaging
>>>> >> location. For example, switching to PyPi for Python packages would be
>>>> >> like switching to Debian for 'native' packages. We don't do that (except
>>>> >> when upstream has disapeared, is acting...)
>>> >
>>> >  This analogy is not quite correct. PyPi is a distribution channel, not a
>>> > downstream. Not that I can think of a better analogy though. But the important
>>> > thing is: the PyPi location is under control of the upstream author, so it is
>>> > equally upstream as the git repo. Brian Thorne (the python-can author) doesn't
>>> > upload tarballs to the bitbucket location (you only get the automatic ones), but
>>> > only to PyPi. So there really is something to be said for using PyPi as the
>>> > download location.
>> I'm following (and contributing to) python-can for more than a year
>> now and this is the first time in my memory that a release was
>> uploaded to PyPi, and this happened cause someone asked for that on a
>> project issue.
>>
>> IMHO, it will not happen in the future again if not prompted by someone.
>>
>> Indeed, I originally submitted the package using bitbucket as a source
>> location, cause it was the only available.
>
>  In that case we should stick to bitbucket as the source. If the next bump is
> still available on pypi we can still switch then.

I've emaled Brian Thorne (maintainer of python-can) about PyPi publishing.

First of all he's very glad to see python-can being included into BR.

Second he agrees, that publishing updates on PyPi is the right
solution and is willing to do so in the future.

Yegor



More information about the buildroot mailing list