Is there a way to do a dry run of "manage.py syncdb", to see what sql
commands it's about to execute?
"./manage.py sqlall" isn't good enough for my purposes because
1) I have to specify the list of applications myself
(although it's easy enough to write a wrapper which will walk across
INSTALLED
Is there a way to tune the way in which runserver decides to restart
itself?
I keep on running into the following issue:
I'm debugging while running through runserver, dropping out into pdb
with a pdb.set_trace where I'm looking for a bug. As I step through
the troublesome code, I notice one thi
Thanks for pointing me at this. I'll try out the patch if I get the
chance.
Toby
Russell Keith-Magee wrote:
> On Wed, Feb 4, 2009 at 11:57 PM, tow wrote:
> >
> > Is there a way to do a dry run of "manage.py syncdb", to see what sql
> > commands it'
I know this seems to be a constant source of confusion; but I seem to
have managed to confuse myself:
class TextData(models.Model):
text = models.TextField(blank=True)
So I have a model with one textfield, whose value can be empty, and I
don't want to worry about distinguishing NULLs and em
I know this seems to be a constant source of confusion; but I seem to
have managed to confuse myself:
class TextData(models.Model):
text = models.TextField(blank=True)
So I have a model with one textfield, whose value can be empty, and I
don't want to worry about distinguishing NULLs and em
e field with no string then go to
> back-end and change the value NULL to 'NOT NULL' to that field.
>
> On Feb 12, 8:35 pm, tow wrote:
>
> > I know this seems to be a constant source of confusion; but I seem to
> > have managed to confuse myself:
>
>
I have a need for a subclass of the URL form field, in a slightly
woolly way.
I need it to only allow addresses which are *public*; that is,
addresses which will have the same behaviour no matter where I am on
the internet. (Yes, I know strictly you can never guarantee this for
any number of reas
If you're running your django server through ./manage.py runserver, is
there a way, from within the django process, to discover which IP
address and port are in use?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"D
ango/core/
servers/basehttp.py")
and s[0].f_code.co_name == "run" and s
[0].f_code.co_argcount == 3):
return s[0].f_locals['server_address']
On Oct 26, 11:34 pm, tow wrote:
> If you're running your django server through ./manage.p
x27;./manage.py runserver other.ip.address:", how do I find
out, from a view inside the django process, that I'm running on
some.other.ip.address:?
Clearly I know what I did, I'm wondering if I can get a view inside
the django process to know what I did.
On Oct 27, 7:17
Toby
On Oct 27, 1:14 pm, Karen Tracey wrote:
> On Tue, Oct 27, 2009 at 8:13 AM, tow wrote:
>
> > Clearly I know what I did, I'm wondering if I can get a view inside
> > the django process to know what I did.
>
> http://docs.djangoproject.com/en/dev/ref/request-res
On Oct 27, 1:53 pm, Christian Joergensen wrote:
>
> You could probably just read it from sys.argv ;)
;-) That had crossed my mind. I think it might actually be the most
robust way!
You have to do a bit of fiddling to make sure you don't grab an
option, and that you don't do this if you're not u
In the ModelForm documentation (https://docs.djangoproject.com/en/dev/
topics/forms/modelforms/) the following snippet appears:
# Create a form to edit an existing Article.
>>> a = Article.objects.get(pk=1)
>>> f = ArticleForm(instance=a)
>>> f.save()
I may be doing something wrong, but I can't s
13 matches
Mail list logo
