-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 11, 2007, at 9:15 AM, Kristján Valur Jónsson wrote:
The SVN repository hasn‘t answered http requests since this
morning. Anyone know what is up with that?
Known breakage. We're working on it.
- -Barry
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 11, 2007, at 10:34 AM, Barry Warsaw wrote:
On Apr 11, 2007, at 9:15 AM, Kristján Valur Jónsson wrote:
The SVN repository hasn‘t answered http requests since this
morning. Anyone know what is up with that?
Known breakage. We're working
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 11, 2007, at 11:10 AM, Barry Warsaw wrote:
I'll take this opportunity to mention that we've ordered a new ssl
cert for our expired one on https. It hasn't arrived yet, but
should within a few days. I'll make another announcement when
Anthony Baxter schrieb:
On behalf of the Python development team and the Python community,
I'm happy to announce the release of Python 2.5.1 (release
candidate 1).
On the 2.5.1 page http://www.python.org/download/releases/2.5.1/
several things are wrong:
- The download link for the AMD64
On 4/11/07, Thomas Heller [EMAIL PROTECTED] wrote:
On the 2.5.1 page http://www.python.org/download/releases/2.5.1/
several things are wrong:
Can someone help fix this? I think Anthony is sleeping right now and
generally pretty busy.
Thanks,
n
___
The title for the highlights page also says Python 2.4
Gustavo
On 4/11/07, Thomas Heller [EMAIL PROTECTED] wrote:
Anthony Baxter schrieb:
On behalf of the Python development team and the Python community,
I'm happy to announce the release of Python 2.5.1 (release
candidate 1).
On the
When pickling instances of an object derived from dict, the pickle in Python
2.5.1c1 calls the object's __getitem__() method. In contrast, earlier versions
of Python incl. 2.5 don't call that method. Below is a minimal example with
outputs. Is the difference in behavior an oversight or new
On 4/9/07, Travis Oliphant [EMAIL PROTECTED] wrote:
Travis, all this is far better and simpler than previous approaches...
Just a few comments
The bufferinfo structure is::
struct bufferinfo {
void *buf;
Py_ssize_t len;
int readonly;
char *format;
int
Lisandro Dalcin wrote:
4) I am not sure about this, but perhaps 'buferingo' should save the
flags passed to 'getbuffer' in a 'flags' field. This can be possibly
needed at 'releasebuffer' call.
The object isn't necessarily providing all the things
that were requested in the flags, so it's
From PEP 3118:
A memory-view object is an extended buffer object that
should replace the buffer object in Python 3K.
typedef struct {
PyObject_HEAD
PyObject *base;
struct bufferinfo view;
int itemsize;
int flags;
} PyMemoryViewObject;
If the purpose is to
Greg Ewing wrote:
From PEP 3118:
A memory-view object is an extended buffer object that
should replace the buffer object in Python 3K.
typedef struct {
PyObject_HEAD
PyObject *base;
struct bufferinfo view;
int itemsize;
int flags;
} PyMemoryViewObject;
If
Travis Oliphant wrote:
Carl Banks wrote:
Travis Oliphant wrote:
Py_BUF_READONLY
The returned buffer must be readonly and the underlying object
should make
its memory readonly if that is possible.
I don't like the if possible thing. If it makes no guarantees, it
pretty much
The pickle issue may be related to revision 53655 fixing a psuedo-bug (it was
arguable whether current or prior behavior was most desirable). Will look at
this more and will report back.
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
Hi
I just got accepted on the google summer of code to work on a project
for python. I just wanted to say hello to everyone out there as i know
i will end up asking a few questions before the summers over.
--
Ryan Kelley
NETS - University of Rhode Island Network Security
14 matches
Mail list logo
