Tristan Seligmann writes:
> With my upstream developer hat on: source packages on PyPI are meant for
> end users to install via pip. They often include generated artifacts, and
> don't include things that aren't intended for installation via pip (tests
> being just one of these).
>
> For distribu
Tristan Seligmann writes:
> With my upstream developer hat on: source packages on PyPI are meant for
> end users to install via pip. They often include generated artifacts, and
> don't include things that aren't intended for installation via pip (tests
> being just one of these).
>
> For distribu
Here is a list of packages that include a test suite on github but not in
the DPMT git.
csvkit https://github.com/onyxfish/csvkit
django-haystackhttps://github.com/toastdriven/django-haystack
django-jinja https://github.com/niwibe/django-jinja
django-recurrence
Hi
Now that debug symbols are automatically generated in -dbgsym packages,
how do you handle the debug
/usr/lib/python2.7/dist-packages/.x86_64-linux-gnu_d.so files?
They used to go in a generic -dbg package.
I'm thinking about rrdtool, and it already has a lot of packages:
https://track
On 22.04.2016 16:58, Jean-Michel Vourgère wrote:
Hi
Now that debug symbols are automatically generated in -dbgsym packages,
how do you handle the debug
/usr/lib/python2.7/dist-packages/.x86_64-linux-gnu_d.so files?
They used to go in a generic -dbg package.
I'm thinking about rrdtool,
5 matches
Mail list logo