At Barry's suggestion (following my PEP 1 updates), I've also updated
the PEP 0 generation machinery to handle an explicit "BDFL-Delegate"
field.
You can see an example here with PEP 3151:
http://www.python.org/dev/peps/pep-3151/
I also updated the 3 PEPs that are on my plate (405, 415 and 3144).
On Sun, May 6, 2012 at 2:56 AM, Barry Warsaw wrote:
> Thanks for doing this update Nick. I have just a few comments.
>
> On May 05, 2012, at 02:57 PM, nick.coghlan wrote:
>
>>+Developers with commit privileges for the `PEP repository`_ may claim
>>+PEP numbers directly by creating and committing
On 05/05/2012 06:17 PM, Stefan Krah wrote:
larry.hastings wrote:
Update Misc/NEWS for issues #14127 and #14705. (And, technically, #10148.)
+ * De-vararg'd PyArg_ParseTupleAndKeywords()
This looks like an accidental commit. Is there an issue number for the
varargs changes (just out of int
larry.hastings wrote:
> Update Misc/NEWS for issues #14127 and #14705. (And, technically, #10148.)
>
> + * De-vararg'd PyArg_ParseTupleAndKeywords()
This looks like an accidental commit. Is there an issue number for the
varargs changes (just out of interest)?
Stefan Krah
_
2012/5/5 larry.hastings :
> http://hg.python.org/cpython/rev/709850f1ec67
> changeset: 76777:709850f1ec67
> user: Larry Hastings
> date: Sat May 05 17:39:09 2012 -0700
> summary:
> Update Misc/NEWS for issues #14127 and #14705. (And, technically, #10148.)
>
> files:
> Modules/po
2012/5/5 larry.hastings :
> http://hg.python.org/cpython/rev/bc6d28e726d8
> changeset: 76776:bc6d28e726d8
> user: Larry Hastings
> date: Sat May 05 16:54:29 2012 -0700
> summary:
> Issue #14705: Add 'p' format character to PyArg_ParseTuple* for bool support.
>
> files:
> Doc/c-ap
dpkg-architecture -qDEB_HOST_MULTIARCH
gives
x86_64-linux-gnu
Installing dpkg-dev fixed the problem. Now both 3.3a3 and a developmental
"clone" work.
There is already a Debian package for 3.3 alpha3.
See http://packages.debian.org/source/experimental/python3.3
A large diff for Debian Python i
On May 05, 2012, at 12:56 PM, Barry Warsaw wrote:
>before the final PEP can be approved. When an `PEP-Czar` header must be
>added to the PEP to record this delegation. The format of this header is
>the same as the `Author` header.
s/When an/A/
-Barry
___
Thanks for doing this update Nick. I have just a few comments.
On May 05, 2012, at 02:57 PM, nick.coghlan wrote:
>+Developers with commit privileges for the `PEP repository`_ may claim
>+PEP numbers directly by creating and committing a new PEP. When doing so,
>+the developer must handle the tas
On May 05, 2012, at 04:04 PM, Christian Heimes wrote:
>The fix needs the dpkg-architecture program. As Tshepang pointed out it
>may not be available on Edward's box. I always install build-essential
>on all development boxes as it includes GCC, make and dpkg-dev.
That's probably it. Certainly Py
Am 05.05.2012 16:13, schrieb Antoine Pitrou:
> Perhaps setup.py should detect that? It shouldn't be too hard to
> parse /etc/debian_version in order to know whether the system is
> multiarch-enabled. That would avoid confusing build failures.
This sounds like a good idea. dpkg-architecture is avai
On Sat, 05 May 2012 16:04:40 +0200
Christian Heimes wrote:
> Am 05.05.2012 15:39, schrieb Antoine Pitrou:
> > On Sat, 05 May 2012 15:31:24 +0200
> > Christian Heimes wrote:
> >> Am 05.05.2012 12:36, schrieb Antoine Pitrou:
> >>>
> >>> Hello,
> >>>
> >>> On Fri, 04 May 2012 14:07:28 -0400
> >>> "E
Am 05.05.2012 15:39, schrieb Antoine Pitrou:
> On Sat, 05 May 2012 15:31:24 +0200
> Christian Heimes wrote:
>> Am 05.05.2012 12:36, schrieb Antoine Pitrou:
>>>
>>> Hello,
>>>
>>> On Fri, 04 May 2012 14:07:28 -0400
>>> "Edward C. Jones" wrote:
Filelist of package libbz2-dev in wheezy of archi
On Sat, May 5, 2012 at 3:43 PM, Tshepang Lekhonkhobe wrote:
> This is likely because you don't have dpkg-dev installed.
http://bugs.python.org/issue13956
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-d
This is likely because you don't have dpkg-dev installed.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Sat, 05 May 2012 15:31:24 +0200
Christian Heimes wrote:
> Am 05.05.2012 12:36, schrieb Antoine Pitrou:
> >
> > Hello,
> >
> > On Fri, 04 May 2012 14:07:28 -0400
> > "Edward C. Jones" wrote:
> >> Filelist of package libbz2-dev in wheezy of architecture amd64
> >>
> >> /usr/include/bzlib.h
> >
Am 05.05.2012 12:36, schrieb Antoine Pitrou:
>
> Hello,
>
> On Fri, 04 May 2012 14:07:28 -0400
> "Edward C. Jones" wrote:
>> Filelist of package libbz2-dev in wheezy of architecture amd64
>>
>> /usr/include/bzlib.h
>> /usr/lib/x86_64-linux-gnu/libbz2.a
>> /usr/lib/x86_64-linux-gnu/libbz2.so
>> /
I just pushed an update to PEP 1 to give additional guidance to core
developers that are directly updating a PEP in Mercurial, to account
for the automatic generation of PEP 0 and to mention the "PEP czar"
role.
Updated PEP:
http://www.python.org/dev/peps/pep-0001/
Changes:
http://hg.python.org/p
On Mon, Apr 30, 2012 at 12:31 PM, Xavier de Gaye wrote:
> Issue http://bugs.python.org/issue13183 raises the point that the step
> command of pdb is broken. This issue is 6 months old. A patch and test
> case have been proposed.
Other pdb commands are also broken for the same reason (no trace
func
Hi,
On Fri, 04 May 2012 14:49:03 -0600
Carl Meyer wrote:
>
> 3) Symlink the interpreter rather than copying. I include this here for
> the sake of completeness, but it's already been rejected due to
> significant problems on older Windows' and OS X.
Perhaps symlinking could be used at least
Hello,
On Fri, 04 May 2012 14:07:28 -0400
"Edward C. Jones" wrote:
> Filelist of package libbz2-dev in wheezy of architecture amd64
>
> /usr/include/bzlib.h
> /usr/lib/x86_64-linux-gnu/libbz2.a
> /usr/lib/x86_64-linux-gnu/libbz2.so
> /usr/share/doc/libbz2-dev
setup.py probably doesn't search i
On Sat, May 5, 2012 at 6:49 AM, Carl Meyer wrote:
> 2) In addition to the above, introduce a versioning marker in the standard
> library (is there one already?) and have some code somewhere (insert
> hand-waving here) check sys.version_info against the stdlib version, and
> fail fast with an unamb
Nick Coghlan gmail.com> writes:
> Personally, I expect that "always update your virtual environment
> binaries after updating the system Python to a new point release" will
> itself become a recommended practice when using virtual environments.
Of course, the venv update tool will need to only u
23 matches
Mail list logo
