During the bug day Andrew Kuchling (I think) mentioned that he was working
on some xmlrpclib issues. I then broached an idea I had a week or so ago to
allow sets to be marshalled as XML-RPC arrays. This was met with some head
scratching by those present. Forging ahead nonetheless, I then propos
musicdev wrote:
> Apologies if my question is a bit novice-ish. I was wondering if there
> was a way of creating a Dynamic Link Library with Python.
>
> Please provide any answers you may have.
Please don't use python-dev for such questions; this is a list for the
development of Python, not the
Hi everyone,
Apologies if my question is a bit novice-ish. I was wondering if there
was a way of creating a Dynamic Link Library with Python.
Please provide any answers you may have.
Warmest Regards,
musicdev
___
Python-Dev mailing list
Python-Dev@py
Martin v. Löwis wrote:
> It complains that, in revision 36760, there was no release24-main
> directory, so it can't know what the history is. I would consider it
> a bug: it could know that release24-maint was a copy of trunk
> which was made after 36760, so it could conclude I meant to
> perform t
Hi
I attended the bug day on Sunday and reviewed six bugs/patches (1212287,
1215184, 1115886, 1372650, 1216942, 878275). So, I'm hoping one of those
nice people who offered 'review 5 get 1 free' might look at a patch of
mine. Test, documentation, and explanatory comments in the tracker are
all t
[EMAIL PROTECTED] wrote:
> Okay, I got it. I was asking for that revision on the release24-maint
> branch, but it was actually applied to the trunk. It shows up now in the
> maintenance branch, but still has to be queried for on the trunk.
My subversion (1.2.3) gives me a slightly more legible o
On 12/5/05, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> On 12/5/05, Jeremy Hylton <[EMAIL PROTECTED]> wrote:
[SNIP]
> I didn't look at the changes much, but from what I saw I think it may
> be better to move the arenas off the branch and onto the head now. It
> appears to be much easier to get right
On 12/5/05, Jeremy Hylton <[EMAIL PROTECTED]> wrote:
> On 12/5/05, James Y Knight <[EMAIL PROTECTED]> wrote:
> >
> > ISTM that having to remember which pointers are arena-allocated and
> > which are normally-refcounted-allocated removes the major gain that
> > an arena method is supposed to bring:
>> svn log --verbose -r 36760
>>
>> When I run it I get this error:
>>
>> svn: REPORT request failed on
'/projects/!svn/bc/36760/python/branches/release24-maint'
>> svn: '/projects/!svn/bc/36760/python/branches/release24-maint' path not
found
Tim> I'm not sure, and
On 12/5/05, James Y Knight <[EMAIL PROTECTED]> wrote:
>
> On Dec 5, 2005, at 8:46 AM, Jeremy Hylton wrote:
> > I can see that problem occurring with an all-or-nothing solution, but
> > not if you have the freedom to allocate from an arena or from some
> > other mechanism. If there are multiple way
[EMAIL PROTECTED]
...
> Wanting to investigate that further, I checked the developer's FAQ and found
> this command to view the checkin history for that rev:
>
>svn log --verbose -r 36760
>
> When I run it I get this error:
>
>svn: REPORT request failed on
> '/projects/!svn/bc/36760/python
On Dec 5, 2005, at 8:46 AM, Jeremy Hylton wrote:
> On 12/5/05, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>
>> Jeremy Hylton wrote:
>> I would expect that you allocate in the process memory that needs to
>> outlive the arena, e.g. python strings. The fundamental problem is
>> that
>> the aren
I'm investigating some problems we're having at work with SIGUSR1 handling.
Our apps tend to see KeyboardInterrupt when sent SIGUSR1 signals. We're
still running 2.3.4 but are in the process of installing/testing 2.4.2.
A couple "find ... | xargs egrep -i usr1" commands in the 2.3 and 2.4 trees
s
On 12/5/05, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Jeremy Hylton wrote:
> I would expect that you allocate in the process memory that needs to
> outlive the arena, e.g. python strings. The fundamental problem is that
> the arena deallocation cannot know whether such memory exists, and what
14 matches
Mail list logo