On 25 September 2013 15:14, Brian May wrote:
> Guess I should file a bug report against python-django then...
>
Submitted as #724637
--
Brian May
> It has that entry, yes, but without the bug report number that was being
> discussed. The point is to immediately record the ITP bug report number
> in that entry of the changelog.
Normally you get an ACK email within a few minutes from opening the ITP. If
you don't, probably there is something
On Sep 18, 2013, at 07:59 AM, Scott Kitterman wrote:
>I also like the approach of we'll add features to python2.7 and call it 2.7
>still because we know there's no 2.8. Seems like not really getting the
>point.
FWIW, I just formally objected to this provision of the PEP in python-dev.
-Barry
On Wed, Sep 25, 2013 at 6:21 PM, Barry Warsaw wrote:
> On Sep 25, 2013, at 06:15 PM, W. Martin Borgert wrote:
>
> >Quoting "Barry Warsaw" :
> >> Sounds a lot like `virtualenv --system-site-packages` right?
> >
> >IMHO, --system-site-packages should be the default.
> >IIRC, it was the default in s
On Sep 19, 2013, at 10:37 AM, Stuart Prescott wrote:
>PPS Virtualenvs are another commonly cited use case for pip, but virtualenvs
>are mostly a short way of saying "we don't care about API stability" (your
>own story of the incompatibilities of django versions is an illustration of
>this); they'r
On Sep 21, 2013, at 04:36 PM, Ben Finney wrote:
>For ‘pbuilder’, you can add a hook that automatically runs Lintian on
>every package it builds. Other packaging tools will surely have a
>similar feature.
sbuild (what I use) runs lintian on the source package automatically AFAIK,
but not on the re
On Sep 21, 2013, at 07:02 AM, Antoine Musso 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 against the 'wnpp' packag
On Wed, Sep 25, 2013 at 12:21:04PM -0400, Barry Warsaw wrote:
> On Sep 25, 2013, at 06:15 PM, W. Martin Borgert wrote:
>
> >Quoting "Barry Warsaw" :
> >> Sounds a lot like `virtualenv --system-site-packages` right?
> >
> >IMHO, --system-site-packages should be the default.
> >IIRC, it was the defa
On Sep 25, 2013, at 06:15 PM, W. Martin Borgert wrote:
>Quoting "Barry Warsaw" :
>> Sounds a lot like `virtualenv --system-site-packages` right?
>
>IMHO, --system-site-packages should be the default.
>IIRC, it was the default in squeeze (1.4.9),
>but is not anymore in wheezy (1.7.1.2). Opinions?
Quoting "Barry Warsaw" :
Sounds a lot like `virtualenv --system-site-packages` right?
IMHO, --system-site-packages should be the default.
IIRC, it was the default in squeeze (1.4.9),
but is not anymore in wheezy (1.7.1.2). Opinions?
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debi
On Sep 18, 2013, at 11:59 PM, Piotr Ożarowski wrote:
>I understand your point and I'm not saying PyPI is something bad,
>I just wish these tools use their own namespace and leave system files
>alone.
This is ultimately where I'd like to see upstream Python packaging going, and
I've had discussion
On Sep 18, 2013, at 12:58 PM, Scott Kitterman wrote:
>P.S. Barry has the wisdom of the ages on his side ;-)
You just couldn't resist, could you? :)
-Barry
signature.asc
Description: PGP signature
On Sep 18, 2013, at 06:33 PM, Paul Wise wrote:
>Barry, I hope this thread has not annoyed you at all :)
FTR it hasn't! I'm sorry I haven't responded previously, and thanks to
paultag for engaging with upstream on the PEP. Work has been incredibly busy
of late and I haven't had many cycles for a
On Wednesday 25 September 2013 15:14:27 Brian May wrote:
> Guess I should file a bug report against python-django then...
Upstream refactored the tests suite during the 1.6 development, so maybe you
could also check if the bug is already fixed and mention in the bug report.
Thanks!
Kind regards
14 matches
Mail list logo
