On Wed, 12 Oct 2011 00:53:52 +0200
victor.stinner wrote:
> http://hg.python.org/cpython/rev/2abd48a47f3b
> changeset: 72878:2abd48a47f3b
> user:Victor Stinner
> date:Wed Oct 12 00:54:35 2011 +0200
> summary:
> Backed out changeset 952d91a7d376
>
> If maxchar == PyUnicode_MAX_
On Tue, 11 Oct 2011 18:22:43 -0400
Barry Warsaw wrote:
> As the BDFOP for PEP 3151, I hereby accept it for inclusion into Python 3.3.
>
> Congratulations to Antoine for producing a great PEP that has broad acceptance
> in the Python development community, with buy-in from all the major
> implemen
As the BDFOP for PEP 3151, I hereby accept it for inclusion into Python 3.3.
Congratulations to Antoine for producing a great PEP that has broad acceptance
in the Python development community, with buy-in from all the major
implementations of Python. Antoine's branch is ready to go and it should
Victor Stinner wrote:
>> Given that I've been working on and maintaining the Python Unicode
>> implementation actively or by providing assistance for almost
>> 12 years now, I've also thought about whether it's still worth
>> the effort.
>
> Thanks for your huge work on Unicode, Marc-Andre!
Thank
On Tue, Oct 11, 2011 at 12:14 PM, Toshio Kuratomi wrote:
> This may not be the preferred manner to write decorators but it's fairly
> straightforward and easy to remember compared to, say, porting away from
> the
> with statement.
>
You can emulate 'with' using decorators, actually, if you don't
On Tue, Oct 11, 2011 at 01:49:43PM +0100, Michael Foord wrote:
> On 10/10/2011 21:21, Giampaolo Rodolà wrote:
> >
> >Toshio Kuratomi wrote:
> >>I have a need to support a small amount of code as far back as python-2.3
> >>I don't suppose you're interested in that as well? ;-)
> >I'm still not sure
On 11/10/2011 16:39, Toshio Kuratomi wrote:
On Tue, Oct 11, 2011 at 12:22:12AM -0400, Terry Reedy wrote:
On 10/10/2011 4:21 PM, Giampaolo Rodolà wrote:
Thanks everybody for your feedback.
I created a gcode project here:
http://code.google.com/p/pycompat/
This project will be easier if the test
On Tue, Oct 11, 2011 at 12:22:12AM -0400, Terry Reedy wrote:
> On 10/10/2011 4:21 PM, Giampaolo Rodolà wrote:
> >Thanks everybody for your feedback.
> >I created a gcode project here:
> >http://code.google.com/p/pycompat/
>
> This project will be easier if the test suite for a particular
> functio
"Martin v. Löwis", 08.10.2011 16:54:
In benchmarking PEP 393, I noticed that many UTF-8 decode
calls originate from C code with static strings, in particular
PyObject_CallMethod. Many of such calls already have been optimized
to cache a string object, however, PyObject_CallMethod remains
unoptimi
2011/10/11 Antoine Pitrou :
> +1 for something more recognizable.
> I think "const string" is more accurate than "identifier" as well.
It should only really be used for identifiers, though, because the
result is interned.
--
Regards,
Benjamin
___
Pyth
On Tue, 11 Oct 2011 09:19:43 -0400
Barry Warsaw wrote:
> On Oct 11, 2011, at 02:36 PM, Hrvoje Niksic wrote:
>
> >On 10/08/2011 04:54 PM, "Martin v. Löwis" wrote:
> >> tmp = PyObject_CallMethod(result, "update", "O", other);
> >>
> >> would be replaced with
> >>
> >>PyObject *tmp;
>
On 10/11/2011 02:45 PM, Amaury Forgeot d'Arc wrote:
It should also check for errors; in this case the initialization is a
bit more verbose:
if (PY_IDENTIFIER_INIT(update) < 0)
;
Error checking is somewhat more controversial because behavior in case
of error differs between situations and codin
On Oct 11, 2011, at 02:36 PM, Hrvoje Niksic wrote:
>On 10/08/2011 04:54 PM, "Martin v. Löwis" wrote:
>> tmp = PyObject_CallMethod(result, "update", "O", other);
>>
>> would be replaced with
>>
>>PyObject *tmp;
>>Py_identifier(update);
>>...
>>tmp = PyObject_Ca
On 10/10/2011 21:21, Giampaolo Rodolà wrote:
Thanks everybody for your feedback.
I created a gcode project here:
http://code.google.com/p/pycompat/
2011/10/8 Antoine Pitrou:
There's also some stuff there that is coded in C, or that will rely on
some functionality of the core interpreter that is
2011/10/11 Hrvoje Niksic
> An alternative I am fond of is to to avoid introducing a new type, and
> simply initialize a PyObject * and register its address. For example:
>
> PyObject *tmp;
> static PyObject *s_update;// pick a naming convention
>
> PY_IDENTIFIER_INIT(update);
> tmp = PyO
On 10/08/2011 04:54 PM, "Martin v. Löwis" wrote:
tmp = PyObject_CallMethod(result, "update", "O", other);
would be replaced with
PyObject *tmp;
Py_identifier(update);
...
tmp = PyObject_CallMethodId(result,&PyId_update, "O", other);
An alternative I am fond o
Vinay Sajip yahoo.co.uk> writes:
Never mind, found the answer from closed issue 9818 - bdist_wininst.vcproj.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailm
The packaging/command folder contains wininst executables with the following
suffixes:
-6.0.exe, -7.1.exe, -8.0.exe, -9.0.exe, -9.0.amd64.exe, -10.0.exe, and
-10.0-amd64.exe.
However, the build files in PC\bdist_wininst only seem to cover building up to
-8.0.exe; there are no build files for -9.0
Hi,
2011/10/11 Vinay Sajip :
> AssertionError: b"Fatal Python error: PyThreadState_Get: no current
> thread\n\r\n
> This application has requested the Runtime to terminate it in an unusual
> way.\nP
> lease contact the application's support team for more information." !=
> b'Fatal P
> ython err
Vinay Sajip wrote:
> test test_capi failed -- Traceback (most recent call last):
> test test_faulthandler failed -- Traceback (most recent call last):
The tests call abort(), and the handling on Windows is slightly
peculiar. See:
http://bugs.python.org/issue9116
http://bugs.python.org/issue11732
I just cloned and built CPython default on Windows 7 32-bit (in a VM). The build
was successful, but I get crashes when running the regression tests:
test test_capi failed -- Traceback (most recent call last):
File "C:\Users\Vinay\Projects\cpython\lib\test\test_capi.py", line 51, in test
_no_Fat
Paul Moore gmail.com> writes:
> To summarise, then:
>
> 1. By using setup.cfg technology, it would be easy enough to zip up a
> binary build in a way that pysetup could unpack and install.
>1a. A packaging command to build such an archive would be worth providing.
> 2. A GUI installer would
22 matches
Mail list logo
