Re: MySQL, Django 1.6, Python3

hi, I was also asking myself if it would be possible to use django 6 python 3 and mysql. Development on mysqldb seems to have paused, so another quesetion: Why not use the mysql connectors from mysql directly: http://www.mysql.com/downloads/connector/python/#downloads They support python 3.3

Re: ModelForm using Model error_messages

This is more or less the idea behind https://code.djangoproject.com/ticket/2 except that the custom error_messages would be defined in ModelForm rather than Model. In my opinion, Model is a terrible place to define user-facing strings such as help_text or error_messages, at best useful to

Re: Testing a django_localflavor_XX package

Le lundi 11 mars 2013 00:42:15 UTC+1, Alon Nisser a écrit : > > how am I supposed to test this? tried following some examples in other > repo, but all failed. I wrote the test itself but it Doesn't run due to > "You must either define the environment variable DJANGO_SETTINGS_MODULE or > call

Re: Documenting lazy() and memoize()

On Mar 11, 2013, at 10:50 AM, Tom Evans wrote: > Hi all > > Someone just asked on users@ "How do I reverse a URL inside > settings.py". I gave a solution (eventually; got it wrong the first > time!) using two functions from django.utils.functional, lazy() and >

Re: Memcache not caching big values (> 1Mb)

On Mon, Mar 11, 2013 at 9:38 AM, Matthew Summers wrote: > On Mon, Mar 11, 2013 at 3:46 AM, Aymeric Augustin > wrote: >> Memcache backend, using python-memcache silently ignores data bigger than >> 1Mb. >> >> >> This is actually a

Re: Memcache not caching big values (> 1Mb)

On Mon, Mar 11, 2013 at 3:46 AM, Aymeric Augustin wrote: > Memcache backend, using python-memcache silently ignores data bigger than > 1Mb. > > > This is actually a limitation of memcached itself. > memcached can be invoked with -I (that is a capital i) to

Documenting lazy() and memoize()

Hi all Someone just asked on users@ "How do I reverse a URL inside settings.py". I gave a solution (eventually; got it wrong the first time!) using two functions from django.utils.functional, lazy() and memoize(). Neither of these two functions are documented. and so aren't part of the API -

Re: Test failures under Oracle

10.3.2013 23:03, Petite Abeille kirjoitti: On Mar 10, 2013, at 9:36 PM, Ian Kelly wrote: These particular lookups have a long history of being tweaked due to users coming up with installations where the existing queries did not work. See tickets #5985, #11017 and

ModelForm using Model error_messages

Django docs state that a ModelForm will automatically set some field attributes for auto generated form fields. Those attributes are limited to : 'required', 'verbose_name', 'help_text', and 'choices' (according to

Re: Permissions model limiting the length of verbose-name

Hi Russell, I'm reordering the text I'm replying to below, to make things clearer. On Monday 11 March 2013 12:14:22 Russell Keith-Magee wrote: > On Mon, Mar 11, 2013 at 5:58 PM, Shai Berger wrote: > > > > I would like to draw your attention to bug #8162[1]. It is old as sin,

Re: Permissions model limiting the length of verbose-name

On Mon, Mar 11, 2013 at 5:58 PM, Shai Berger wrote: > Hi all, > > I would like to draw your attention to bug #8162[1]. It is old as sin, and > annoying as virtue. > You won't get any argument from me on this analysis. > The gist of it is: because, for all models, when the

Permissions model limiting the length of verbose-name

Hi all, I would like to draw your attention to bug #8162[1]. It is old as sin, and annoying as virtue. The gist of it is: because, for all models, when the admin is present, permissions are created automatically; because these permissions are named "Can %s %s" % (action, model.verbose_name);

Re: Django sanctioned extensions

Hi, I maintain the IBM DB2 Django backend (ibm_db_django) project(http://code.google.com/p/ibm-db/). We have been maintaining this extension since Django-1.0 and have always kept it up-to-date. The http://code.google.com/p/ibm-db/ project also provides a Python DBI compliant driver, based on

Re: Memcache not caching big values (> 1Mb)

Hi Luciano, > Memcache backend, using python-memcache silently ignores data bigger than 1Mb. This is actually a limitation of memcached itself. > 1 - Compress cache data > https://code.djangoproject.com/ticket/16116 > Because body page has a good compression rate this feature helps a lot on >

Re: MySQL, Django 1.6, Python3

On 11 mars 2013, at 00:32, Norberto Bensa wrote: > I wanted to run Django with Python 3 but mysql was a showstopper until today. Hi Norberto, Since MySQLdb wasn't ported to Python 3 yet, this isn't officially supported at this time. I've filed a ticket so we don't forget

Re: Update on localflavor move

Hi Aymeric & Adrian, I didn't see any further discussion or consensus on the issue of the generic localflavor. The 1.5 docs and (accelerated) deprecation of localflavor are a little hazy regarding the generic localflavor. The 1.5 docs say that it hasn't been removed (yet), but doesn't say it