Hi all --
OK, so I've run into some problems setting up the new box, so this
isn't going to happen tonight. (If anyone can help me get Django's
authentication handler working with Apache 2.2 / mod_python 3.3,
please get in touch!)
So chances are I'll put this off until after the sprint. Sorry fo
Howdy folks --
I'm about to move djangoproject.com (and subdomains) to a new server.
The short version of the changes:
DNS should update within the hour, but if it doesn't, you'll want to
put this in your /etc/hosts (or equivalent)::
64.207.133.18 djangoproject.com
64.207.133.18 www.dja
So the sprint is ambling along right now. If you didn't get the memo,
the place to be is irc://irc.freenode.net/django-sprint
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to thi
On 9/14/07, Ludvig Ericson <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I can't seem to understand how to do this with newforms 'properly':
>
> 1) A base model, call it Apartment.
> 2) A model called Person, who lives in an Apartment, i.e., a
> ForeignKey(Apartment)
>
> Now, what I want to do is to g
Here are two quick suggestions:
form_for_model in the trunk supports a 'fields' argument. What do you
guys think about adding an 'exclude_fields' argument ? It is very
handy when you want to have all but one or two fields from a model in
a form.
In the same vein, I have studied the queries genera
Hello,
I can't seem to understand how to do this with newforms 'properly':
1) A base model, call it Apartment.
2) A model called Person, who lives in an Apartment, i.e., a
ForeignKey(Apartment)
Now, what I want to do is to get a form like the admin has with
edit_inline, so something like:
On Thu, 2007-09-13 at 14:02 +0200, Tomas Kopecek wrote:
[...]
> I think that blocktrans in its current state is more obstacle than
> helper for me and introduces lot of quite unnecessary code. Furthermore
> I see priority in usability and simplicity for designers than for
> translators.
Well r
On Thu, 2007-09-13 at 12:09 +0200, Michael Radziej wrote:
> Hi Malcolm,
>
> I'd like to work a bit on the Autoescaping patch at the sprint (adding
> newforms handling, selftests for newforms). Do you have any new stuff for it
> or any comments? Or would you like to do it yourself?
I'll send you
I use newforms-admin branch and I like it very much. And I have some
ideas for possible improvements for internationalization.
1. Capitalized verbose names for models
Now the preferred format is:
class Contact(models.Model):
email = models.CharField(verbose_name=_('email'))
class ContactFo
On Sep 5, 9:32 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> I propose Friday, September 14.
Just a quick note for anyone in Scotland: there's a small group of us
(four at the mo) in Edinburgh joining the sprint from 7PM (GMT+1)
onwards. We're meeting at my flat so if anyone in the area wan
On 9/13/07, Wensing, Matthew (CNI-Palm Beach) <[EMAIL PROTECTED]> wrote:
> Can someone tell me if there's a GeoDjango IRC channel? Who can I talk to
> about the project?
The main developers on the project are Jeremy Dunck (jdunck) and
Justin Bronn (jbronn); they both read django-dev and should p
Can someone tell me if there's a GeoDjango IRC channel? Who can I talk
to about the project?
Thanks,
Matt
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send e
Hey Mike,
> To use Koen's example, he has not implement regex lookups yet, and he wishes
> to tell the test not to fail as it simply not implemented. In my opinion the
> test SHOULD fail because well the test is to see whether or not this feature
> is implement, and its not. Now i'm not familiar
Hi,
On Thu, Sep 13, Russell Keith-Magee wrote:
> Regarding the implementation - I'm sure the easiest solution will be
> to put an 'if not mysql' check around the failing tests. However, my
> preferred solution would fix this at the output layer, rather than the
> test layer - i.e., let the tests
Malcolm Tredinnick napsal(a):
> The standard argument against allowing arbitrary constructs inside the
> translation block (things like {{var|filter}}) is that translators have
> to type that string *exactly* into their translation in order for it to
> appear. Since those strings can get quite co
Hey everyone,
I've been keeping an eye on the list for a little while now, and felt I was
ready to add in my thoughts.
In regard to this implementation I think care has to be taken that the
option not be presented as a coders easy way out so-to-speak, the issue
being that this implementation coul
I am having a similar problem with a custom db2 backend I am working
on too.
Maybe it can be linked in the implementation to some backend flag (in
the backends DatabaseFeatures) stating that deferred constraint
checking is not (entirely) implemented ? This as opposed to hardcoding
"mysql" in the t
On 9/13/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> So, I'd appeal for skipping tests that cannot succeed, like in this
> case.
This is ticket #4788, and it has been accepted as an idea. We just
need an implementation. If you want this for a sprint activity, it's
all yours.
Regarding the
On 9/13/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> So, I'd appeal for skipping tests that cannot succeed, like in this
> case.
This is ticket #4788, and it has been accepted as an idea. We just
need an implementation. If you want this for a sprint activity, it's
all yours.
Regarding the
Hi Malcolm,
I'd like to work a bit on the Autoescaping patch at the sprint (adding
newforms handling, selftests for newforms). Do you have any new stuff for it
or any comments? Or would you like to do it yourself?
Michael
--
noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg -
Tel
Hi,
we know that the tests for fixtures fail for MySQL (innodb) since MySQL checks
foreign key constraints too early. OK. But how do we deal with the
testsuite?
I'd like that the tests always succeed for any database backend
(unless something is broken in the code or in the installation that ne
21 matches
Mail list logo
