Re: Adding Support for PyMySQL (for Python 3)

2011-12-13 Thread Ian Clelland 
On Thu, Dec 8, 2011 at 7:46 AM, Ian Clelland  wrote:

>
>
> On Thursday, December 8, 2011, Jens Diemer 
> wrote:
> > Am 07.12.2011 21:38, schrieb Ian Clelland:
> >>
> >> PyMySQL is a pure python implementation of PEP 249 for MySQL, and
> supports
> >> Python 2.4 - 3.2, and MySQL 4.1 and higher.
> >
> > Another goal of PyMySQL would be to use Django + MySQL with PyPy, isn't
> it?
> >
>
> You know, I hadnt thought of it, but that would definitely go a long way
> towards making that possible!
>
> Ill see if I can polish up a proposal for splitting up the backend code
> into SQL and driver code, but I'll try to get a separate pymysql backend up
> in a repository somewhere for people to try out as well.


There is now a PyMySQL backend available on Github --
https://github.com/clelland/django-mysql-pymysql

It leverages a lot of the code in django.db.backends.mysql; importing it
where it can, and duplicating it where it has to. I hope to have a proposal
by the weekend for splitting out the database adapter code from the
backends, and then this project can get a lot lighter :)

If you use my patches to PyMySQL, at https://github.com/clelland/PyMySQL,
then the full django unit test suite (from trunk) will pass under Python
2.6.7. There are some character set handling issues with the upstream
version at the moment.

(And at this point, I'm veering dangerously close to django-users
territory; If needed, I'll continue this thread with an announcement there)

-- 
Regards,
Ian Clelland


-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django-nonrel patches

2011-12-13 Thread Wilfred Hughes 
On Dec 12, 4:46 pm, Karen Tracey  wrote:>
>
> This SELECT:
>
> >  {'sql': u'SELECT "vortaro_car"."id", "vortaro_car"."name",
> > "vortaro_car"."owner_id" FROM "vortaro_car" WHERE
> > "vortaro_car"."owner_id" IN (1)',
> >  'time': '0.001'},
> >  {'sql': u'DELETE FROM "vortaro_car" WHERE "id" IN (1)', 'time':
> > '0.000'},
>
[...]
>
> Django did explicitly find-and-delete the Car. It did not rely on the
> underlying database to do that.

Ah, absolutely right. I'll file a bug our end for this. Cheers.

Wilfred

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Add disabled cookies as possible cause of csrf token 403 debug page

2011-12-13 Thread Jacob Kaplan-Moss 
On Tue, Dec 13, 2011 at 12:23 AM, h3  wrote:
> I tried and double checked the given possibilities and ended up
> finding that cookies were diabled on my phone..
>
> Would be nice if there was a hint about this in the debug page.

That's a good idea. It looks like we're actually capturing that
information in the middleware itself -- see REASON_NO_CSRF_COOKIE in
django/middleware/csrf.py -- but not doing anything with it in the
debug page.

Can you open a ticket so that we don't forget?

Thanks,

Jacob

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Add disabled cookies as possible cause of csrf token 403 debug page

2011-12-13 Thread Florian Apolloner 
Hi,

as usual: patches are more than welcome :)

Cheers,
Florian

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/o-JLBD7RdIoJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.