On Wed, Oct 10, 2007 at 07:41:14AM -, Tomi Pieviläinen wrote:
>
> It seems that if you have Django installed for Python 2.5, the
> internal help system breaks up a bit. To reproduce just open the
> normal shell (not through manage.py), type "help()" and "modules".
>
> Setting DJANGO_SETTINGS
On Sat, Sep 29, 2007 at 08:01:12PM -0700, [EMAIL PROTECTED] wrote:
>
> Doh, it was not mod_wsgi, or localemiddleware, it was the
> set_language_view() that after rev 6177 requires a post request
I see in the Backwards-incompatible changes says:
The old behaviour meant that state (the locale
On Sun, Aug 26, 2007 at 04:47:28AM -0500, James Bennett wrote:
>
> On 8/26/07, Sandro Dentella <[EMAIL PROTECTED]> wrote:
> > While I completely agree on what you say, I'd point out that not only
> > differences from 0.96 to trunk should be noted, if possible, but
> Our philosophy so far has been that documentation improvements are
> something that *all* current Django users should benefit from,
> including users of trunk *and* users of the latest release. If we find
> typos, or we take the time to write up better explanations of things,
> we want to have t
> The problem is that there is a userbase of thousands and a lot of
> evidence to suggest that most people don't read mailing list threads
> that they didn't start themselves. Yes, almost everybody reading this is
so let's come to the surface... i use signals. Mainly pre-save / post-save.
And jus
On Mon, Feb 26, 2007 at 06:16:31PM -, [EMAIL PROTECTED] wrote:
>
> I would like to see http://code.djangoproject.com/ticket/3297
> implemented before 0.96 if possible.
I definitely agree. And more It's a working one!
I think that newforms are the true change in this releise. We need to try
On Tue, Feb 27, 2007 at 11:26:11AM -0600, Jacob Kaplan-Moss wrote:
>
> On 2/27/07, Seattle Daniel <[EMAIL PROTECTED]> wrote:
> > As I read it, there is not a way to force InnoDB to check constraints
> > at commit. And once there is it will be quite some time before the
> > mass of MySQL instances
syncdb complain the table already exits, when tries to
create the middle table for the second time...]
sandro
*:-)
(*) not really, that was true with oldforms, now you must define a
formfield_callback...
--
Sandro Dentella *:-)
http://www.tksql.orgTkSQL Hom
I'd like to take your attention on a side effect of missing
FloatField.formfield(): CharField is used in newforms that means that
null=True, blank=True will use an empty strings that correctly makes
PostgreSql quite angry... (sqlite doesn't bother...)
Digging into the open tickets I see the reaso
el and form_for_instance.
What is the testing you think you need?
I'd be glad to give feedback so that it can be pushed into svn.
sandro
*:-)
--
Sandro Dentella *:-)
http://www.tksql.orgTkSQL Home page - My GPL work
--~--~-~--~~~---~--~~
Y
PythonPath "['c:/myproject/test/site'] + sys.path"
> PythonHandler django.core.handlers.modpython
> SetEnv DJANGO_SETTINGS_MODULE haltnet_site.settings
> PythonDebug On
> PythonAutoReload On
>
>
>
ppearing up to 36-40
hours later and messages never arrived to the list.
sandro
*;-)
--
Sandro Dentella *:-)
http://www.tksql.orgTkSQL Home page - My GPL work
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
12 matches
Mail list logo