no I mean, really, read http://pkg-perl.alioth.debian.org/git.html
* they have a tool that automatically creates (and push) a new package
from CPAN, and sets everything up with the team standards; the same
should happen for python and pypi. and there is tool (dpt) to manage
the other common packag
Back in June 2014, I filed bug #751908, which Piotr closed as wontfix. This
is really related to an open question in Python packaging concerning a
standard naming scheme for packages which provide Python applications
(e.g. /usr/bin scripts) whether or not they also provide importable libraries,
al
[Barry Warsaw, 2015-08-06]
> Should there be a naming convention for Python packages which only provide an
> executable?
everything that doesn't match python[\d.]*- is fine IMHO.
If "tox" is too generic, use tox-python
--
Piotr Ożarowski Debian GNU/Linux Developer
www.oza
On 06/08/15 15:50, Barry Warsaw wrote:
> The example that sparked issue #751908 was tox, which when I initially
> packaged it, I called the binary package python-tox. I did this because,
> while the package does not provide any publicly importable modules, I felt it
> was presumptuous to claim a r
On Thu, Aug 6, 2015 at 17:08:35 +0200, Piotr Ożarowski wrote:
> [Barry Warsaw, 2015-08-06]
> > Should there be a naming convention for Python packages which only provide
> > an
> > executable?
>
> everything that doesn't match python[\d.]*- is fine IMHO.
>
> If "tox" is too generic, use tox-py
On Aug 06, 2015, at 04:20 PM, Simon McVittie wrote:
>Policy has this to say on the subject of a different flat global namespace:
>
>"When scripts are installed into a directory in the system PATH, the
>script name should not include an extension such as .sh or .pl that
>denotes the scripting langu
On Aug 06, 2015, at 05:08 PM, Piotr Ożarowski wrote:
>everything that doesn't match python[\d.]*- is fine IMHO.
Here's some language for DPP:
=== modified file 'debian/python-policy.sgml'
--- debian/python-policy.sgml 2015-02-27 23:09:27 +
+++ debian/python-policy.sgml 2015-08-06 19:04:4
Hey,
> I believe that we are still using SVN but maybe the switch to git will
> be done during the next Debconf.
>
> Personnaly, I don't really care if a package is team-maintained or
> not. It is better if it is and it will allow you to find another sponsor
> in case your regular sponsor is unre
On Aug 06, 2015, at 11:42 AM, Sandro Tosi wrote:
>no I mean, really, read http://pkg-perl.alioth.debian.org/git.html
Thanks for the link Sandro.
Reading this, I think it's on par with our
https://wiki.debian.org/Python/GitPackaging by which I mean it's prescriptive
of how to do common tasks in a
Package: wnpp
Severity: wishlist
Owner: Brian May
* Package name: python-django-cors-headers
Version : 1.1.0
Upstream Author : Otto Yiu
* URL : https://github.com/ottoyiu/django-cors-headers/
* License : MIT
Programming Lang: Python2 and Python3
Description
10 matches
Mail list logo
