ITP: astroml -- Machine learning for Astronomy

2014-08-04 Thread Francisco Gallardo lópez
Package: wnpp Severity: wishlist Package name : astroml Version : 0.2.1 Upstream Author : Jake Vanderplas vanderp...@astro.washington.edu URL : http://jakevdp.github.com License : BSD Description : This is a Python Machine Learning library for astronomy. I would like to create a package for

Re: Help needed to test packages with Django 1.7

2014-08-04 Thread Thomas Goirand
On 08/03/2014 03:27 PM, Raphael Hertzog wrote: On Sun, 03 Aug 2014, Brian May wrote: Django 1.7 final isn't even released upstream, and therefore, downstream projects didn't even try to run against it. There *will* be issues we will have to deal with. 85 packages is quite something. I'm ok,

Re: Help needed to test packages with Django 1.7

2014-08-04 Thread Barry Warsaw
On Aug 04, 2014, at 11:05 PM, Thomas Goirand wrote: Well, I'm doing my best to add Python 3 support everywhere I can. \o/ I've been doing this for months already. I know it wont be possible to fix everything. Currently, I have 2 blockers which I am working on: - python-memcache - beautifulsoup

Re: Help needed to test packages with Django 1.7

2014-08-04 Thread Thomas Goirand
On 08/04/2014 11:30 PM, Barry Warsaw wrote: On Aug 04, 2014, at 11:05 PM, Thomas Goirand wrote: Well, I'm doing my best to add Python 3 support everywhere I can. \o/ I've been doing this for months already. I know it wont be possible to fix everything. Currently, I have 2 blockers which

Re: Help needed to test packages with Django 1.7

2014-08-04 Thread Thomas Kluyver
On 4 August 2014 10:29, Thomas Goirand z...@debian.org wrote: Also, fixing version 3 of beautifulsoup doesn't look very easy. It needs sgmllib, which is removed from Python 3, and it doesn't feel right to maintain sgmllib as a Python module for Python 3 (I tried, and with a few hacks, it

policy for source package names

2014-08-04 Thread Antonio Valentino
Hi list, I read in [1] and [2] that binary packages with public modules should have the python- (or python3-) prefix in the name. I'm wondering if the same naming rules should be used for source packages. I'm preparing some new packages so I would like to be sure I'm using the correct naming

Re: policy for source package names

2014-08-04 Thread Vincent Cheng
On Mon, Aug 4, 2014 at 2:17 PM, Antonio Valentino antonio.valent...@tiscali.it wrote: Hi list, I read in [1] and [2] that binary packages with public modules should have the python- (or python3-) prefix in the name. I'm wondering if the same naming rules should be used for source packages.

Re: policy for source package names

2014-08-04 Thread Antonio Valentino
Hi Vincent, Il 05/08/2014 00:04, Vincent Cheng ha scritto: On Mon, Aug 4, 2014 at 2:17 PM, Antonio Valentino antonio.valent...@tiscali.it wrote: Hi list, I read in [1] and [2] that binary packages with public modules should have the python- (or python3-) prefix in the name. I'm wondering if

Re: policy for source package names

2014-08-04 Thread Ben Finney
Vincent Cheng vch...@debian.org writes: […] just don't pick a source package name that's already taken, and pick one that is relevant to your package […] I further advise: Try to avoid names which are too broad (e.g. “coverage” for a Python-specific code coverage package), or names which can

Re: policy for source package names

2014-08-04 Thread Scott Kitterman
On Tuesday, August 05, 2014 11:54:37 Ben Finney wrote: Vincent Cheng vch...@debian.org writes: […] just don't pick a source package name that's already taken, and pick one that is relevant to your package […] I further advise: Try to avoid names which are too broad (e.g. “coverage” for a