Package: python3-pyramid
Version: 1.5.1+dfsg-2
Severity: normal
Dear Maintainer,
There is no trace of pyramid/scaffolds/{starter, alchemy, zodb} being
included within the package, even though they are mentionned in the
pcreate manpage. I've checked, the setup.py from the original tarball
FYI: The status of the stdeb source package
in Debian's testing distribution has changed.
Previous version: 0.8.2-3
Current version: 0.8.2-4
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
Package: python-pip
Version: 1.5.6-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
$ pip install --user youtube-dl
Downloading/unpacking youtube-dl
Downloading youtube_dl-2014.11.16-py2.py3-none-any.whl (691kB): 691kB
downloaded
Installing collected packages: youtube-dl
I just fixed this in pip’s develop branch. It’s not released yet though, but it
will be in pip 6.0.
---
Donald Stufft
PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
___
Python-modules-team mailing list
Your message dated Mon, 17 Nov 2014 19:33:51 +
with message-id e1xqs3b-00063k...@franck.debian.org
and subject line Bug#751827: fixed in python-pip 1.5.6-3
has caused the Debian Bug report #751827,
regarding python-virtualenv: version of pip in virtualenvs fails to uninstall
some packages
to
The weird package relationships are due to the interaction between historical
baggage, Debian Python policy, and the port of the cli to Python 3.
python-foo should only be for Python 2 compatible libraries, while python3-foo
is for the Python 3 compatible libraries. Back when python-virtualenv
Please don’t change the default. There is no way in pip to turn that flag *off*
again once it's turned on and any flag added by Debian will be Debian specific
and confuse people. We (pip) plan to make this change on our own at which point
it will then be able to be done in a consistent way.
---
On Mon, 17 Nov 2014 16:47:54 -0500 Donald Stufft don...@stufft.io wrote:
Please donât change the default. There is no way in pip to turn that flag
*off*
again once it's turned on and any flag added by Debian will be Debian specific
and confuse people. We (pip) plan to make this change on our
On 18 November 2014 07:53, Barry Warsaw ba...@debian.org wrote:
The typical solution is to move the /usr/bin script (and manpage, etc.)
into a
separate binary package, and it makes the most sense to call this
'virtualenv'. Because /usr/bin/virtualenv is a Python 3 script, it
Depends on
On Nov 18, 2014, at 09:39 AM, Brian May wrote:
For another solution, have a look at django-admin, provided by the
django-common package. You can call it using any of the following ways:
brian@aquitard:~$ django-admin# run as sh; autodetect python
Yep, that autodetect is clever. Such a
Hi Barry (2014.11.17_22:53:01_+0200)
The question still remains: how best to upgrade people who have
/usr/bin/virtualenv provided by python-virtualenv in Wheezy, so that they now
get /usr/bin/virtualenv provided by virtualenv in Jessie? Using Recommends
was an attempt at that, but clearly
On 5 November 2014 12:11, Collin Anderson cmawebs...@gmail.com wrote:
There might be a problem because it looks like it conflicts with
python-mysqldb.
Yes, it's a 100% compatible fork intended to replace python-mysqldb. Same
python package name and everything. We could decide to only include
12 matches
Mail list logo
