On Thu, Jun 19, 2008 at 8:18 PM, nirinA raseliarison
<[EMAIL PROTECTED]> wrote:
> hello all,
> i tried to build Python3.0b1 but the make process hangs
> while running:
Building with gcc 4.3 is buggy. See
http://mail.python.org/pipermail/python-3000/2008-April/012965.html.
--
Cheers,
Benjamin P
hello all,
i tried to build Python3.0b1 but the make process hangs
while running:
./python -E ./setup.py build
breaking the building with ctrl-C, i have:
gcc -pthread -Xlinker -export-dynamic -o python
Modules/python.o
libpython3.0.a -lpthread -
On Thu, Jun 19, 2008 at 6:11 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I haven't had the time to look into this, but it sounds unintuitive to
> drop __reduce_ex__ which is supposed to be the "extended" IOW "newer"
> version of the API compared to __reduce__ which was deemed to be
> missing
On Thu, Jun 19, 2008 at 3:43 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> From: "Guido van Rossum" <[EMAIL PROTECTED]>
>>
>> I haven't had the time to look into this, but it sounds unintuitive to
>> drop __reduce_ex__ which is supposed to be the "extended" IOW "newer"
>> version of the API co
From: "Guido van Rossum" <[EMAIL PROTECTED]>
I haven't had the time to look into this, but it sounds unintuitive to
drop __reduce_ex__ which is supposed to be the "extended" IOW "newer"
version of the API compared to __reduce__ which was deemed to be
missing something.
Right. The version argum
I haven't had the time to look into this, but it sounds unintuitive to
drop __reduce_ex__ which is supposed to be the "extended" IOW "newer"
version of the API compared to __reduce__ which was deemed to be
missing something.
On Thu, Jun 19, 2008 at 2:19 PM, Alexandre Vassalotti
<[EMAIL PROTECTED]>
Any comment on the proposed changes? Well if no-one objects, I would
like to move forward and implement these changes:
- Deprecate __reduce_ex__ and copyreg.pickle in 2.6 and 3.0 (with a
planned removal in 3.1).
- Make __reduce__ raise a TypeError on the condition previously
described in 3.0.
2008/6/19 Marcin 'Qrczak' Kowalczyk <[EMAIL PROTECTED]>:
> What is the current equivalent of:
> modulePy = Py_InitModule(\"_ko_unpickle\", ko_py_unpickle_defs);
> ?
Ok, I found it out myself:
modulePy = PyModule_Create(&ko_py_unpickle_module);
if (modulePy == NULL) ...;
statu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 19, 2008, at 4:43 AM, Paul Moore wrote:
On 19/06/2008, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community,
I am
happy to announce the fir
What is the current equivalent of:
modulePy = Py_InitModule(\"_ko_unpickle\", ko_py_unpickle_defs);
?
--
Marcin Kowalczyk
[EMAIL PROTECTED]
http://qrnik.knm.org.pl/~qrczak/
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/ma
On 19/06/2008, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On behalf of the Python development team and the Python community, I am
> happy to announce the first beta releases of Python 2.6 and Python 3.0.
Any ETA for Windows builds? The web pages s
11 matches
Mail list logo
