Greg Ewing wrote:
> Travis Oliphant wrote:
>
>> It is more convenient to store any slicing information (so a memory
>> view object could store an arbitrary slice of another object) as
>> offsets, lengths, and skips which can be used to adjust the memory
>> buffer returned by base.
>
> What happe
Travis Oliphant wrote:
> Py_BUF_SIMPLE --- you are requesting the simplest possible (0x00)
>
> Py_BUF_WRITEABLE -- get a writeable buffer (0x01)
>
> Py_BUF_READONLY -- get a read-only buffer(0x02)
I don't see how these three form a progression.
From the other things you say, it appe
Hello all.
I made two checkins to the 25 maintainance branch before Martin kindly pointed
out to me that it is frozen.
These are quite simple fixes to real crashes I have experienced. The fix in
frameobject.c will be necessary if you work with opcodes > 128, which we
routinely do at CCP J. Sec
Travis Oliphant wrote:
> It is more convenient to store any slicing information (so a memory view
> object could store an arbitrary slice of another object) as offsets,
> lengths, and skips which can be used to adjust the memory buffer
> returned by base.
What happens if the base object change
On 4/13/07, Tim Peters <[EMAIL PROTECTED]> wrote:
> One low-effort approach is to use a general root-finding algorithm and
> build ln(x) on top of exp() via (numerically) solving the equation
> exp(ln(x)) == x for ln(x). That appears to be what Don Peterson did
> in his implementation of transcend
Trent Mick schrieb:
> Is it generally accepted to just checkin obviously non-controversial
> fixes (*) (as long as there is no code freeze), or is it still preferred
> that I go through adding a patch to the SF tracker and getting review?
>
> Trent
>
> (*) In my case a tweak to the old VC6 Wind
Is it generally accepted to just checkin obviously non-controversial
fixes (*) (as long as there is no code freeze), or is it still preferred
that I go through adding a patch to the SF tracker and getting review?
Trent
(*) In my case a tweak to the old VC6 Windows build files to ensure a
clean
[Raymond Hettinger]
> ...
> Likewise, consider soliciting Tim's input on how to implement the ln()
> operation. That one will be tricky to get done efficiently and correctly.
One low-effort approach is to use a general root-finding algorithm and
build ln(x) on top of exp() via (numerically) solvi
Paul Moore wrote:
> On 09/04/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
>
>>>I have skimmed (briefly, I'll admit!) the pre-PEP, but I've found it
>>>extremely difficult to find a simple example of the basic (in my view)
>>>use case of an undifferentiated block of bytes.
>>>
>>
>>This is a grea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 13, 2007, at 11:07 AM, Jean-Paul Calderone wrote:
> Likely differing buffering behavior. Prior to Linux 2.6, the pipe
> implementation allowed only a single buffer (that is, the bytes from
> a single write call) in a pipe at a time, and blocke
If anyone is interested in participating in discussing the details of the
PyDoc rewrite/refactoring I've been working on, a discussion is being
started on the doc-sig list.
[EMAIL PROTECTED]
The goal of this discussion will be to get it to a final finished form so a
patch can be submi
On Fri, 13 Apr 2007 11:02:01 -0400, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>On Apr 13, 2007, at 10:57 AM, Jean-Paul Calderone wrote:
>>>I don't know if this is caused by a bug in the Mac's pty
>>>implementation or something we're doing wrong on tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 13, 2007, at 10:57 AM, Jean-Paul Calderone wrote:
>> I don't know if this is caused by a bug in the Mac's pty
>> implementation or something we're doing wrong on that platform. I
>> played around with several modifications to pty.fork() on the
On Fri, 13 Apr 2007 10:32:28 -0400, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>I've been getting some test failures in Python 2.5 svn head on Mac OS
>X 10.4.9 which I'm not getting on Linux (Ubuntu feisty beta).
>test_sqlite and test_zipimport both fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been getting some test failures in Python 2.5 svn head on Mac OS
X 10.4.9 which I'm not getting on Linux (Ubuntu feisty beta).
test_sqlite and test_zipimport both fail, however, when run in
verbose mode (e.g. ./python.exe Lib/test/test_sqli
On 4/13/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> >> int PyObject_GetContiguous(PyObject *obj, void **buf, Py_ssize_t
> >> *len,
> >>int fortran)
> >>
> >> Return a contiguous chunk of memory representing the buffer. If a
> >> copy is made then return 1.
On 4/13/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > I didn't find getbuildinfo2.c in the source. Can some one tell me if
> > I am missing some thing here? Are there any additional steps need to
> > follow on windows?
>
> It's a generated file. Search all build description files for that
On 4/13/07, Andrew Clover <[EMAIL PROTECTED]> wrote:
> Jason Orendorff wrote:
> > I don't suppose you'd be willing to update it for Python 2.5, would you?
>
> Can do, but at this point I'm not aware of any work having been done on
> the issues listed there between the 2.3 and 2.5 releases.
I've be
On Thu, Apr 12, 2007 at 12:12:48PM -0400, Terry Reedy wrote:
> | Open http://www.python.org/2.5/highlights.html
> |
> | The title of the page says "Highlights: Python 2.4"
Ah, so it's a 2.5 page, not a 2.5.1 page; that's why my grep didn't
find it. Fixed now; thanks!
--amk
Jason Orendorff wrote:
> I don't suppose you'd be willing to update it for Python 2.5, would you?
Can do, but at this point I'm not aware of any work having been done on
the issues listed there between the 2.3 and 2.5 releases.
The danger is people may be used to the "wrong" minidom behaviours,
20 matches
Mail list logo
