-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have 10MB pickled structure generated in Python 2.7. I only use basic
types (no clases) like sets, dictionaries, lists, strings, etc.
The pickle stores a lot of strings. Some of them should be bytes,
while other should be unicode. My idea is to
On 22/02/2011 12:14, Jesus Cea wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have 10MB pickled structure generated in Python 2.7. I only use basic
types (no clases) like sets, dictionaries, lists, strings, etc.
The pickle stores a lot of strings. Some of them should be bytes,
while
On Tue, 22 Feb 2011 13:14:18 +0100
Jesus Cea j...@jcea.es wrote:
This seems to be a bug in Python 3.2. Any suggestion?.
Report an issue and investigate :)
Antoine.
___
Python-Dev mailing list
Python-Dev@python.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/02/11 13:20, Michael Foord wrote:
Traceback (most recent call last):
File stdin, line 1, inmodule
ValueError: operation forbidden on released memoryview object
That seems like an odd error, but the decision was made that Python 2
PS: Just checked... Python 3.1.3 imports the pickle just fine. So busy
migrating my projects to 3.2 (it was my compromise two years ago :), I
don't have time to debug this :).
I hope you do have a time to open an issue, though :-)
Eli
___
Python-Dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/02/11 15:32, Eli Bendersky wrote:
PS: Just checked... Python 3.1.3 imports the pickle just fine. So busy
migrating my projects to 3.2 (it was my compromise two years ago :), I
don't have time to debug this :).
I hope you do have a time to
On Fri, Feb 18, 2011 at 4:00 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Fri, Feb 18, 2011 at 14:41, anatoly techtonik techto...@gmail.com wrote:
Do you have a public list of stuff to be done (i.e. Roadmap)?
BTW, what is the size of Mercurial clone for Python repository?
There is a TODO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/22/2011 9:41 AM, anatoly techtonik wrote:
On Fri, Feb 18, 2011 at 4:00 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Fri, Feb 18, 2011 at 14:41, anatoly techtonik techto...@gmail.com wrote:
Do you have a public list of stuff to be done
Greetings!
According to these release notes in Python 3.0, %-formatting will be
going away.
http://docs.python.org/release/3.0.1/whatsnew/3.0.html#pep-3101-a-new-approach-to-string-formatting
However, I was unable to find any further evidence of actual deprecation
in 3.1 or 3.2... does
On Mon, Feb 21, 2011 at 15:34, David Claridge da...@daave.com wrote:
Hi,
I was wondering if there is some reason why C API functions like
PyObject_CallMethod[1] and PySys_GetObject[2] take char* arguments
rather than const char*s? If there is some reason these methods will
modify their
On Tue, Feb 22, 2011 at 10:43, Ethan Furman et...@stoneleaf.us wrote:
Greetings!
According to these release notes in Python 3.0, %-formatting will be going
away.
http://docs.python.org/release/3.0.1/whatsnew/3.0.html#pep-3101-a-new-approach-to-string-formatting
However, I was unable to
On Tue, Feb 22, 2011 at 10:55 AM, Brett Cannon br...@python.org wrote:
On Mon, Feb 21, 2011 at 15:34, David Claridge da...@daave.com wrote:
Hi,
I was wondering if there is some reason why C API functions like
PyObject_CallMethod[1] and PySys_GetObject[2] take char* arguments
rather than
On 02/22/2011 01:43 PM, Ethan Furman wrote:
Greetings!
According to these release notes in Python 3.0, %-formatting will be
going away.
http://docs.python.org/release/3.0.1/whatsnew/3.0.html#pep-3101-a-new-approach-to-string-formatting
However, I was unable to find any further evidence of
On 02/22/2011 01:55 PM, Brett Cannon wrote:
On Mon, Feb 21, 2011 at 15:34, David Claridge da...@daave.com
mailto:da...@daave.com wrote:
Hi,
I was wondering if there is some reason why C API functions like
PyObject_CallMethod[1] and PySys_GetObject[2] take char* arguments
On Tue, 22 Feb 2011 11:06:41 -0800
Guido van Rossum gu...@python.org wrote:
Probably because (a) the person who first wrote them used char* instead of
const char*, and (b) it gives us API flexibility by not promising to not
alter the char array at some point in the future.
I'm sorry,
On Tue, Feb 22, 2011 at 2:09 PM, Eric Smith e...@trueblade.com wrote:
Also changing it now would be a giant hassle, leading to so-called const
poisoning where many, many APIs need to be changed before everything would
again work.
The poisoning will not break any users of the API, though, since
Reid Kleckner, 22.02.2011 21:21:
On Tue, Feb 22, 2011 at 2:09 PM, Eric Smith wrote:
Also changing it now would be a giant hassle, leading to so-called const
poisoning where many, many APIs need to be changed before everything would
again work.
The poisoning will not break any users of the
On Tue, 22 Feb 2011 21:48:51 +0100
Stefan Behnel stefan...@behnel.de wrote:
Reid Kleckner, 22.02.2011 21:21:
On Tue, Feb 22, 2011 at 2:09 PM, Eric Smith wrote:
Also changing it now would be a giant hassle, leading to so-called const
poisoning where many, many APIs need to be changed before
On 2011-02-22, at 21:55 , Antoine Pitrou wrote:
On Tue, 22 Feb 2011 21:48:51 +0100
Stefan Behnel stefan...@behnel.de wrote:
Reid Kleckner, 22.02.2011 21:21:
On Tue, Feb 22, 2011 at 2:09 PM, Eric Smith wrote:
Also changing it now would be a giant hassle, leading to so-called const
poisoning
On Tue, Feb 22, 2011 at 1:17 PM, Xavier Morel python-...@masklinn.net wrote:
On 2011-02-22, at 21:55 , Antoine Pitrou wrote:
On Tue, 22 Feb 2011 21:48:51 +0100
Stefan Behnel stefan...@behnel.de wrote:
Reid Kleckner, 22.02.2011 21:21:
On Tue, Feb 22, 2011 at 2:09 PM, Eric Smith wrote:
Also
On Wed, Feb 23, 2011 at 4:51 AM, Brett Cannon br...@python.org wrote:
The very long term view is for %-formatting to go away, but that's as far as
the thinking has gone. There are currently no plans to introduce any
deprecation warning, and I highly doubt we will even remove the feature in
Also changing it now would be a giant hassle, leading to so-called
const poisoning where many, many APIs need to be changed before
everything would again work.
We have been adding const to many places over the years. I think the
specific case was just missed (i.e. nobody cared about adding
On Wed, 23 Feb 2011 07:52:23 +1000
Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Feb 23, 2011 at 4:51 AM, Brett Cannon br...@python.org wrote:
The very long term view is for %-formatting to go away, but that's as far as
the thinking has gone. There are currently no plans to introduce any
Though I do not get that warning -- which compiler and version issues
it? Is it a C or a C++ compiler?
Well, which warning are you talking about?
I think Guido assumed that the OP was getting actual complaints from
some actual compiler - else he wouldn't have asked the question.
However, he
The very long term view is for %-formatting to go away
Add to that that this view isn't universally shared among contributors.
Many of us would rather see % formatting stay indefinitely. I regularly
use it for new code.
Regards,
Martin
___
Python-Dev
On Wed, Feb 23, 2011 at 8:03 AM, Antoine Pitrou solip...@pitrou.net wrote:
I think there are many people still finding %-style more practical for
simple uses,
A lot of the sting went out of that objection when field autonumbering
was added to new-style formatting ('%s' % (obj,) vs
One of the students on an introductory Python 3 class asks a very good question
about string formatting. This could be because the course materials are
misleading, so I would like to understand. It would appear from tests that
{0[X]}.format(...) first tries to convert the string X to in
On Mon, Feb 21, 2011 at 6:34 PM, David Claridge da...@daave.com wrote:
..
I was wondering if there is some reason why C API functions like
PyObject_CallMethod[1] and PySys_GetObject[2] take char* arguments
rather than const char*s?
The later is addressed by issue 1699259
If you compile
#include Python.h
int main()
{
PyObject_CallMethod(0, stdin, stdin);
}
you get
a.cc: In function ‘int main()’:
a.cc:5: warning: deprecated conversion from string constant to ‘char*’
a.cc:5: warning: deprecated conversion from string constant to ‘char*’
Since most
On Tue, Feb 22, 2011 at 6:01 PM, Steve Holden st...@holdenweb.com wrote:
... It would appear from tests
that {0[X]}.format(...) first tries to convert the string X to in
integer. If it succeeds then __getitem__() is called with the integer as an
argument, otherwise it is called with the string
On Tue, 22 Feb 2011 18:08:01 -0500
Alexander Belopolsky alexander.belopol...@gmail.com wrote:
On Mon, Feb 21, 2011 at 6:34 PM, David Claridge da...@daave.com wrote:
..
I was wondering if there is some reason why C API functions like
PyObject_CallMethod[1] and PySys_GetObject[2] take char*
Quoting PEP 3101:
An example of the 'getitem' syntax:
My name is {0[name]}.format(dict(name='Fred'))
It should be noted that the use of 'getitem' within a format string
is much more limited than its conventional usage. In the above example,
the string 'name' really is the literal
On Feb 22, 2011, at 3:08 PM, Eric Smith wrote:
Quoting PEP 3101:
An example of the 'getitem' syntax:
My name is {0[name]}.format(dict(name='Fred'))
It should be noted that the use of 'getitem' within a format string
is much more limited than its conventional usage. In the
On Tue, Feb 22, 2011 at 6:18 PM, Antoine Pitrou solip...@pitrou.net wrote:
..
I don't think it's a good idea to backport visible API changes.
(someone successfully compiling on 2.7.N could then have users
complaining that compilation fails on 2.7.N-1).
Moreover, it doesn't really fix a bug.
On Tue, Feb 22, 2011 at 6:01 PM, Steve Holden st...@holdenweb.com wrote:
... It would appear from tests
that {0[X]}.format(...) first tries to convert the string X to in
integer. If it succeeds then __getitem__() is called with the integer as an
argument, otherwise it is called with the
On Tue, 2011-02-22 at 23:03 +0100, Antoine Pitrou wrote:
On Wed, 23 Feb 2011 07:52:23 +1000
Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Feb 23, 2011 at 4:51 AM, Brett Cannon br...@python.org wrote:
The very long term view is for %-formatting to go away, but that's as far
as
the
Le mardi 22 février 2011 à 18:30 -0500, Alexander Belopolsky a écrit :
On Tue, Feb 22, 2011 at 6:18 PM, Antoine Pitrou solip...@pitrou.net wrote:
..
I don't think it's a good idea to backport visible API changes.
(someone successfully compiling on 2.7.N could then have users
complaining
Even if it is eventually decided not to backport those patches to 2.7,
it would be nice if the documentation could be updated to indicate
that strings passed to those functions won't be modified, so that API
users like myself can feel a little safer when passing literals in,
without having to
On Tue, Feb 22, 2011 at 6:36 PM, Antoine Pitrou solip...@pitrou.net wrote:
..
To quote the message above: someone successfully compiling on 2.7.N
could then have users complaining that compilation fails on 2.7.N-1.
(note: *N-1*)
I missed that. Yes, this is a valid concern. I change my vote
I don't think it's a good idea to backport visible API changes.
(someone successfully compiling on 2.7.N could then have users
complaining that compilation fails on 2.7.N-1).
+1. If it was a bug fix (which it isn't), having this kind of breakage
would be fine, of course (i.e. code relying on
On 2/22/2011 6:32 PM, Senthil Kumaran wrote:
On Tue, Feb 22, 2011 at 6:01 PM, Steve Holdenst...@holdenweb.com wrote:
... It would appear from tests
that {0[X]}.format(...) first tries to convert the string X to in
integer. If it succeeds then __getitem__() is called with the integer as an
On 2/22/2011 6:28 PM, Steve Holden wrote:
On Feb 22, 2011, at 3:08 PM, Eric Smith wrote:
Quoting PEP 3101:
An example of the 'getitem' syntax:
My name is {0[name]}.format(dict(name='Fred'))
It should be noted that the use of 'getitem' within a format string
is much more limited
You should maybe backport this fix to Python 3.2.
Le mardi 22 février 2011 à 20:24 +0100, giampaolo.rodola a écrit :
Author: giampaolo.rodola
Date: Tue Feb 22 20:24:33 2011
New Revision: 88505
Log:
In FTP.close() method, make sure to also close the socket object, not only
the file.
On Tue, Feb 15, 2011 at 6:30 PM, Martin v. Löwis mar...@v.loewis.de wrote:
I'm going to perform a Debian upgrade of svn.python.org on Friday,
between 9:00 UTC and 11:00 UTC. I'll be disabling write access during
that time. The outage shouldn't be longer than an hour.
This may have caused some
On Feb 22, 2011, at 5:43 PM, Nick Coghlan wrote:
On Tue, Feb 15, 2011 at 6:30 PM, Martin v. Löwis mar...@v.loewis.de wrote:
I'm going to perform a Debian upgrade of svn.python.org on Friday,
between 9:00 UTC and 11:00 UTC. I'll be disabling write access during
that time. The outage shouldn't
2011/2/22 brett.cannon python-check...@python.org:
Author: brett.cannon
Date: Tue Feb 22 20:12:43 2011
New Revision: 88503
Log:
Add lib2to3.__main__ to make it easier for debugging purposes to run 2to3.
Please revert this and do it in the sandbox.
Added:
Jesus Cea writes:
PPS: If there is consensus that this is a real bug, I would create an
issue in the tracker and try to get a minimal testcase.
All bugs are issues, but not all issues are bugs.
Please don't wait for consensus or even a second opinion to file the
issue.
It's reasonable for
On Tue, Feb 22, 2011 at 9:31 PM, Stephen J. Turnbull step...@xemacs.org wrote:
Jesus Cea writes:
PPS: If there is consensus that this is a real bug, I would create an
issue in the tracker and try to get a minimal testcase.
All bugs are issues, but not all issues are bugs.
Please don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/02/11 03:31, Stephen J. Turnbull wrote:
Please don't wait for consensus or even a second opinion to file the
issue.
It's reasonable for a new Python user to ask whether something is a
bug or not, but if somebody with your experience and
I'll do.
2011/2/23 Victor Stinner victor.stin...@haypocalc.com:
You should maybe backport this fix to Python 3.2.
Le mardi 22 février 2011 à 20:24 +0100, giampaolo.rodola a écrit :
Author: giampaolo.rodola
Date: Tue Feb 22 20:24:33 2011
New Revision: 88505
Log:
In FTP.close() method,
Jesus Cea writes:
Every time I read a message from [long, incompletewink list] and
so many others python-devs (not an exhaustive list, if you are not
there, you probably should, sorry :), I feel I am faking my
knowledge of Python :-). I am a pretender :).
Sure. I suspect even some of
Am 23.02.2011 02:43, schrieb Nick Coghlan:
On Tue, Feb 15, 2011 at 6:30 PM, Martin v. Löwis mar...@v.loewis.de wrote:
I'm going to perform a Debian upgrade of svn.python.org on Friday,
between 9:00 UTC and 11:00 UTC. I'll be disabling write access during
that time. The outage shouldn't be
You're sure this will not cause tedious conflicts with backports?
Georg
On 22.02.2011 16:56, giampaolo.rodola wrote:
Author: giampaolo.rodola
Date: Tue Feb 22 16:56:20 2011
New Revision: 88501
Log:
smtlib.py PEP8 normalization via pep8.py script.
Modified:
This commit introduced tabs, at least in dynload_dl.c.
Georg
On 23.02.2011 00:16, victor.stinner wrote:
Author: victor.stinner
Date: Wed Feb 23 00:16:19 2011
New Revision: 88516
Log:
Issue #3080: Remove unused argument of _PyImport_GetDynLoadFunc()
The first argument, fqname, was not
54 matches
Mail list logo
