On Wed, Jun 27, Ian Kelly wrote:
> Hmm, the test seems to pass for me in mysql.
grmbl, it happened *again*
I use git-svnimport to sync the svn with my git repository, and it seems to
fail around every 6 months under unknown circumstances (probably something
with merges), only when I don't
On Wed, 2007-06-27 at 14:12 -0600, Ian Kelly wrote:
> On 6/27/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > it seems I'm the only one to run the test suite with mysql ;-)
> >
> > Ticket #4711 - http://code.djangoproject.com/ticket/4711
> >
> > Currently the tests break because
On 6/27/07, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
>
> Thanks for bringing this up Russ. The problem at the moment is that
> the admin doesn't look at any of the inlines when figuring out what
> javascript to load, so if your inlines have date fields, the js
> doesn't get loaded unless the
On Jun 27, 8:07 pm, Robert Coup <[EMAIL PROTECTED]>
wrote:
> Marty Alchin wrote:
> > Regardless though, I think Jacob makes the best point so far: Django's
> > cache system is robust enough to handle it if you pick a decent
> > backend. And if there's a need to make the built-in options more
> >
On 6/27/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
> Hi,
>
> it seems I'm the only one to run the test suite with mysql ;-)
>
> Ticket #4711 - http://code.djangoproject.com/ticket/4711
>
> Currently the tests break because mysql returns 0 or 1 for a BooleanField,
> not False or True.
Carl Karsten wrote:
> This just came up - let me know if you need more info.
> im CarlFK in #django
>
> Carl K
>
> [EMAIL PROTECTED]:~/django/django-src$
> ...
> Updated to revision 5556.
>
>
> [EMAIL PROTECTED]:~/django$ django-admin.py startproject foo
> [EMAIL PROTECTED]:~/django$ cd foo
>
This just came up - let me know if you need more info.
im CarlFK in #django
Carl K
[EMAIL PROTECTED]:~/django/django-src$
...
Updated to revision 5556.
[EMAIL PROTECTED]:~/django$ django-admin.py startproject foo
[EMAIL PROTECTED]:~/django$ cd foo
[EMAIL PROTECTED]:~/django/foo$ python
Marty Alchin wrote:
> I remembered seeing that FastCGI can not only run as prefork,
Thank goodness.
> but defaults to it.
Thank *goodness*.
One day mutable-shared-state, preemptive multithreading will be looked down
on as the ugly, awful, historical accident that it is.
The signs are good
Thanks.
On Jun 27, 1:31 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On 6/27/07, Kevin Tonon <[EMAIL PROTECTED]> wrote:
>
> > I'm using Django 0.91
>
> Hi, Kevin. Please ask this question on django-users. The
> django-developers list is for people developing Django itself rather
> than
On 6/27/07, Kevin Tonon <[EMAIL PROTECTED]> wrote:
> I'm using Django 0.91
Hi, Kevin. Please ask this question on django-users. The
django-developers list is for people developing Django itself rather
than using Django for a project.
When you do, it'd help to include the template you're
Hi,
I'm using Django 0.91
More or less, this is what I'm doing:
from django.core.template import Library, Node
register = Library()
class MyNode(Node):
def __init__(self, foo):
self.foo = foo
print 'foo' * 100
def render(self, context):
print 'bar' * 100
> > The biggest hurdle to dbsettings at this point is that it caches
> > settings in a standard Python module, which only exists within a
> > single process. This was all well and good while developing it, but
> > people are now starting to try it under mod_python, which (depending
> > on the
On 6/26/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On 6/20/07, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> >
> > Yep. None of the javascript stuff really works right now. The calendar
> > and picker widgets for date and time fields, for instance, are broken.
>
> Sounds like a good
On Wed, Jun 27, 2007 at 02:41:15PM -, Donny wrote:
>
> On Jun 26, 11:28 am, "Marty Alchin" <[EMAIL PROTECTED]> wrote:
> > The biggest hurdle to dbsettings at this point is that it caches
> > settings in a standard Python module, which only exists within a
> > single process. This was all well
On Jun 26, 11:28 am, "Marty Alchin" <[EMAIL PROTECTED]> wrote:
> The biggest hurdle to dbsettings at this point is that it caches
> settings in a standard Python module, which only exists within a
> single process. This was all well and good while developing it, but
> people are now starting to
Marty Alchin wrote:
> Regardless though, I think Jacob makes the best point so far: Django's
> cache system is robust enough to handle it if you pick a decent
> backend. And if there's a need to make the built-in options more
> robust, we can deal with that when the need arises.
>
What about
2007/6/26, Jacob Kaplan-Moss <[EMAIL PROTECTED]>:
>
> On 6/26/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > I'm just curious, I've read somewhere (maybe here) that the
> > contrib.comments package need to be rewritten in order to allow more
> > flexibility (like user.get_profile) and to use
On Jun 27, 8:46 pm, "Paul Bowsher" <[EMAIL PROTECTED]> wrote:
> No, this is meant to go at the end of a long view function
> def index(request):
> # Lots of code
> render_to_response_with_req(request, 'home/index.html', {'a': 'dict'})
Firstly, you should be `return`ing this request. ;)
Some time ago I overviewed model history and I realized that I don't
like a general idea - one model that logs everything. At that time
Django was studied how to create models dynamically (http://
code.djangoproject.com/wiki/DynamicModels) and I wrote small history
app for our purposes (of
No, this is meant to go at the end of a long view function
def index(request):
# Lots of code
render_to_response_with_req(request, 'home/index.html', {'a': 'dict'})
etc.
On 6/27/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
>
> On 6/26/07, Paul Bowsher <[EMAIL PROTECTED]> wrote:
>
20 matches
Mail list logo
