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

[Arnout Vandecappelle <arnout@mind.be>]

On 02-01-16 22:50, Angelo Compagnucci wrote:
> Yegor, Arnout, All
> 
> 2016-01-02 22:04 GMT+01:00 Arnout Vandecappelle <arnout@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.

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF