Re: Disabling pip for root?

2013-09-21 Thread Antoine Musso
Le 20/09/13 10:29, Thomas Goirand a écrit : > It's really not hard to package some Python modules for Python. Having a > tool that does it automatically - even not very well -, like debpear > does, can solve this kind of trouble. Giving access to this kind of > tools to a wide user base can also he

Re: PEP 453 affects Debian packaging of Python packages

2013-09-21 Thread Elena ``of Valhalla''
On 2013-09-20 at 15:44:05 -0700, Thomas Kluyver wrote: > Elena: > > there is an UpstreamGuide_ on the wiki: > > So promote it! I'm pretty sure I've never seen that URL before. that's exactly what I was doing :) there *is* a problem with the way debian documentation has naturally grown to a poin

Re: Reverting switch to dh-python for pyflakes

2013-09-21 Thread Dmitrijs Ledkovs
Hello, On 21 September 2013 05:02, Thomas Goirand wrote: > Hi, > > I'm having issues with backporting pyflakes 0.7.3-1 to Ubuntu precise. > It would help a lot if you reverted your switch to dh-python. Do you > think that's possible? > No, I will not revert that. Instead dh-python should be back

Re: Best practices for data files in /usr/share

2013-09-21 Thread Jakub Wilk
On Sat, Sep 21, 2013 at 11:36:05PM +0600, Andrey Rahmatullin wrote: So, what are the best practices for moving data files out of the module directories? This is how we do it in Sphinx: 1) There's only one statement that uses __file__ (thanks, upstream!): http://sources.debian.net/src/sphinx/1.

Best practices for data files in /usr/share

2013-09-21 Thread Andrey Rahmatullin
Hello. I'm packaging a new version of python-babel and as it now builds 2.x and 3.x packages I decided to move the locale data into /usr/share and package it separately. Currently the data is installed using 'package_data' setup() argument and accessed via os.path.dirname(__file__). I've added som

Re: How to help with sphinx 1.2?

2013-09-21 Thread Dmitry Shachnev
Hi Jakub, On Mon, Sep 16, 2013 at 3:51 PM, Jakub Wilk wrote: > Anyway, here's a list of bugs you might want to fix before uploading Sphinx > 1.2 (beta or not) to unstable: > http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=python-modules-t...@lists.alioth.debian.org;tag=sphinx1.2 > https://bitb

Re: PEP 453 affects Debian packaging of Python packages

2013-09-21 Thread Ben Finney
Andrey Rahmatullin writes: > On Sat, Sep 21, 2013 at 04:36:23PM +1000, Ben Finney wrote: > > Instead, when you first create the package, edit ‘debian/changelog’ > > and make “Initial Debian package of ‘foo’ (Closes: bug#NN)” the > > very first bullet point in your first changelog entry. Then

Re: PEP 453 affects Debian packaging of Python packages

2013-09-21 Thread Andrey Rahmatullin
On Sat, Sep 21, 2013 at 04:36:23PM +1000, Ben Finney wrote: > > I keep forgetting filling an ITP. It is usually caught on final review > > because for some reason lintian is not being run by default by my > > packaging chain :-( > For ‘pbuilder’, you can add a hook that automatically runs Lintian

Re: PEP 453 affects Debian packaging of Python packages

2013-09-21 Thread Andrey Rahmatullin
On Sat, Sep 21, 2013 at 08:50:46AM +0200, Etienne Millon wrote: > > I find the ITP/wnpp annoying as well. I usually end up browsing > > http://www.debian.org/devel/wnpp/ , opening all links then searching > > for my package :-] I then bootup an instance and try to remember > > to report the bug a