Am 16.09.11 00:42, schrieb Nick Coghlan:
On Fri, Sep 16, 2011 at 7:39 AM, "Martin v. Löwis
wrote:
Thinking about this, the following may work:
- ASCIIObject: state, length, hash, wstr*, data follow
- SingleBlockUnicode: ASCIIObject, wstr_len, utf8*, utf8_len, data
follow
- UnicodeObject: Sin
On Fri, Sep 16, 2011 at 8:44 AM, Albert Zeyer wrote:
> Hi list,
>
> I thought it would be nice in Python to allow some sort of meta coding
> (which goes far ahead of simple function descriptors).
>
> The most straight forward way would be to allow operations on the AST.
1. This kind of suggestion
2011/9/15 Albert Zeyer :
> Hi list,
>
> I thought it would be nice in Python to allow some sort of meta coding
> (which goes far ahead of simple function descriptors).
>
> The most straight forward way would be to allow operations on the AST.
>
> I wrote a small patch for CPython 2.7.1 which, for e
Hi list,
I thought it would be nice in Python to allow some sort of meta coding
(which goes far ahead of simple function descriptors).
The most straight forward way would be to allow operations on the AST.
I wrote a small patch for CPython 2.7.1 which, for each code object,
adds the related AST
On Fri, Sep 16, 2011 at 7:39 AM, "Martin v. Löwis" wrote:
> Thinking about this, the following may work:
> - ASCIIObject: state, length, hash, wstr*, data follow
> - SingleBlockUnicode: ASCIIObject, wstr_len,
> utf8*, utf8_len, data follow
> - UnicodeObject: SingleBlockUnicode
I like it. If we start which such optimization, we can also also remove data
from strings allocated by the new API (it can be computed: object pointer +
size of the structure). See my email for my proposition of structures:
Re: [Python-Dev] PEP 393 review
Thu Aug 25 00:29:19 2011
I agree
Le jeudi 15 septembre 2011 17:50:41, Martin v. Löwis a écrit :
> In reviewing memory usage, I found potential for saving more memory for
> ASCII-only strings. (...)
>
> typedef struct {
> PyObject_HEAD
> Py_ssize_t length;
> union {
> void *any;
> Py_UCS1 *latin1;
On Thu, Sep 15, 2011 at 8:50 AM, "Martin v. Löwis" wrote:
> In reviewing memory usage, I found potential for saving more memory for
> ASCII-only strings. Both Victor and Guido commented that something like
> this be done; Antoine had asked whether there was anything that could
> be done. Here is t
On 9/15/2011 11:50 AM, "Martin v. Löwis" wrote:
To comply with the C aliasing rules, the structures would look like this:
typedef struct {
PyObject_HEAD
Py_ssize_t length;
union {
void *any;
Py_UCS1 *latin1;
Py_UCS2 *ucs2;
Py_UCS4 *ucs4;
} data;
Py_hash_t hash;
int state; /* may include SSTATE_
On 15/09/2011 17:23, Éric Araujo wrote:
Le 13/09/2011 18:34, Michael Foord a écrit :
On 13/09/2011 16:57, Éric Araujo wrote:
(IIRC PyPI will require us to play games to have both
2.x and 3.x versions of distutils2.)
What I'm doing for unittest2.
[...]
2) I have a pypi project called unittestpy
Jesus Cea wrote:
> I am seeing a few commits related to clang (a C compiler, alternative
> to GCC), but we ¿only? have a buildbot using clang as the compiler.
>
> If there is interest, I would deploy 32 and 64 bits buildbots under my
> current OpenIndiana buildbot.
I think it makes sense. clang
+2 for promoting naming consistency and putting metadata where it's supposed
to be.
--Yuval
On Sep 15, 2011 9:23 AM, "Éric Araujo" wrote:
> Le 13/09/2011 18:34, Michael Foord a écrit :
>> On 13/09/2011 16:57, Éric Araujo wrote:
>>> (IIRC PyPI will require us to play games to have both
>>> 2.x and
On Thu, Sep 15, 2011 at 12:23 PM, Éric Araujo wrote:
> I think it would make more sense to
> push 2.x-compatible and 3.x-compatible sdists to PyPI (with an
> appropriate 'Programming Language :: Python :: 2' or '3' classifier) and
> have the download tools be smart.
FWIW, I prefer this as well.
Le 13/09/2011 18:34, Michael Foord a écrit :
> On 13/09/2011 16:57, Éric Araujo wrote:
>> (IIRC PyPI will require us to play games to have both
>> 2.x and 3.x versions of distutils2.)
>
> What I'm doing for unittest2.
> [...]
> 2) I have a pypi project called unittestpy3k that holds the Python 3
In reviewing memory usage, I found potential for saving more memory for
ASCII-only strings. Both Victor and Guido commented that something like
this be done; Antoine had asked whether there was anything that could
be done. Here is the idea:
In an ASCII-only string, the UTF-8 representation is sha
I added a section on porting guidelines to the PEP, resulting
from my own porting experience. Please review.
http://www.python.org/dev/peps/pep-0393/#porting-guidelines
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pytho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, pals.
I am seeing a few commits related to clang (a C compiler, alternative
to GCC), but we ¿only? have a buildbot using clang as the compiler.
If there is interest, I would deploy 32 and 64 bits buildbots under my
current OpenIndiana buildbot.
Another update - I've added proper documentation. Now the code should be
pretty much complete - all that's missing is the necessary bits and pieces
to build it on Windows.
Cheers,
Nadeem
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pytho
Jai Sharma wrote:
> Hi,
>
> I am facing a memory leaking issue with codecs. I make my own ABC class and
> register it with codes.
>
> import codecs
> codecs.register(ABC)
>
> but I am not able to remove ABC from memory. Is there any alternative to do
> that.
The ABC codec search function gets a
Below is reference pattern:
0: _ --- [-] 4 : 0xa70ca44, 0xa70e79c, 0xe5c602c, 0xe6219bc
1: a [-] 4 tuple: 0xab11c5c*3, 0xe72a43c*3, 0xe73c16c*3, 0xe73c1bc*3
2: aa [-] 4 function: ABC.l_codecs.decode...
3: a3 [S] 2 dict of class: ..Codec, ..Codec
4: aab [-] 4 types.MethodT
20 matches
Mail list logo
