On Mon, May 25, 2009 at 08:39:39PM -0700, Ryan Boggs wrote:
> I just tested this with django without the workaround and it works.
> If this is committed, then the patch for django can be removed.
I will commit this version instead later today.
f.-
Index: Makefile
I just tested this with django without the workaround and it works.
If this is committed, then the patch for django can be removed.
Was that the only spot in mxDateTime that was using the bm_free method?
Thanks,
Ryan
On Mon, May 25, 2009 at 7:23 PM, Federico G. Schwindt wrote:
> On Mon, May 25,
On Mon, May 25, 2009 at 12:30:36PM -0400, Ian Darwin wrote:
> Ryan Boggs wrote:
>> Sorry, I don't mean to spam.
>>
>> I've updated the tar ball to list me as the maintainer (with Darrin's
>> approval).
>>
>> I also updated the MESSAGE file with the correct path to the online
>> documentation and a
Ryan Boggs wrote:
Sorry, I don't mean to spam.
I've updated the tar ball to list me as the maintainer (with Darrin's approval).
I also updated the MESSAGE file with the correct path to the online
documentation and a message indicating changes between versions 0.96
and 1.0 with a link to help wi
Sorry, I don't mean to spam.
I've updated the tar ball to list me as the maintainer (with Darrin's approval).
I also updated the MESSAGE file with the correct path to the online
documentation and a message indicating changes between versions 0.96
and 1.0 with a link to help with migration.
Pleas
Attached are the files I used to create the new 1.0.2 package for
testing. I patched the file in question to only use the lambda
function since it seems to work ok.
Please let me know if more is needed.
Thanks,
Ryan
On Sun, May 24, 2009 at 11:18 AM, Ryan Boggs wrote:
> EUREKA. I found it.
>
>
EUREKA. I found it.
Starting on line 451 in
/usr/local/lib/python2.5/site-packages/django/http/multipartparser.py,
there is a try statement as follows:
try:
from mx.TextTools import FS
self._fs = FS(boundary).find
except ImportError:
self._fs = lambda data: data.find(boun
Ryan & Alexandre, nice work so far!
On Sat, May 23, 2009 at 05:22:36PM -0700, Ryan Boggs wrote:
> So you are using Postgresql as you back end DB. Have you tried using
> py-psycopg2 with Django? I've been using it for my testing without
> problems and it doesn't seem to rely on py-mxDateTime.
So
Ian,
So you are using Postgresql as you back end DB. Have you tried using
py-psycopg2 with Django? I've been using it for my testing without
problems and it doesn't seem to rely on py-mxDateTime.
Still, even though removing py-mxDateTime allows Django 1.0+ to work,
that's not the desired work a
Ryan Boggs wrote:
To Alexandre:
Thanks for that link. I do not use py-mxDateTime normally so I never
installed it on my test machine. Once I did, I started receiving
those errors that both Ian and Darrin were reporting with Django 1.0+.
py-mxDateTime contains the mxTextTools library that seems
To Alexandre:
Thanks for that link. I do not use py-mxDateTime normally so I never
installed it on my test machine. Once I did, I started receiving
those errors that both Ian and Darrin were reporting with Django 1.0+.
py-mxDateTime contains the mxTextTools library that seems to be (at
least) on
Darrin Chandler wrote:
On Sat, May 16, 2009 at 04:05:10PM -0700, Ryan Boggs wrote:
Hey Darrin,
If no one else is interested, I would like to work on it.
Where exactly is the crash happening in Admin?
In 1.0 the crash happened trying to save a new user, iirc. For 1.0.2 you
could save
Hello,
maybe this could give you an hint:
http://code.djangoproject.com/ticket/11001.
I ran across this issue with django 1.0.2 on 4.4 and 4.5. the
mxTextTools.so library (installed with the py-mxDateTime package as a
dependency of pylint) was clearly the cause of the crash. no idea why
how
When I was testing a few months ago, I never ran into that problem
either. I'm wondering if it has to do with the database connector or
something in the like.
When I tested, I was using Python2.5 with Postgresql as the database.
What were you guys using?
On Sat, May 16, 2009 at 7:16 PM, Matt Jib
I cannot replicate this on 1.0.2, which I have been using without
issue for a while.
On Sat, May 16, 2009 at 6:36 PM, Darrin Chandler
wrote:
> On Sat, May 16, 2009 at 04:05:10PM -0700, Ryan Boggs wrote:
>> Hey Darrin,
>>
>> If no one else is interested, I would like to work on it.
>>
>> Where exa
On Sat, May 16, 2009 at 04:05:10PM -0700, Ryan Boggs wrote:
> Hey Darrin,
>
> If no one else is interested, I would like to work on it.
>
> Where exactly is the crash happening in Admin?
In 1.0 the crash happened trying to save a new user, iirc. For 1.0.2 you
could save a new user, but further e
Hey Darrin,
If no one else is interested, I would like to work on it.
Where exactly is the crash happening in Admin?
Thanks,
Ryan
-- Forwarded message --
From: Darrin Chandler
To: ports@openbsd.org
Date: Fri, 15 May 2009 15:52:56 -0700
Subject: www/py-django
Hi,
I'm the mainta
17 matches
Mail list logo