different domains = different settings.py = different urls.py
On Dec 23, 12:30 pm, Dan Ger wrote:
> Hi, I have searched to no avail and decided to post here.
>
> I have a django app that is going to have multiple domain names and
> would very much like to use the domain name in the urls.py to he
a python string is immutable
using the + operation on it causes strings to be copied into memory
and made into another immutable string... which doesn;t save much...
but the next uses of + requires another copy, and the next so on...
where as using % does copy once
On Aug 22, 4:49 am, Joost Casse
random person: "i need help"
magus: gives technical answer
random person: does understand python
magus: points to docs
random person: you are rude
On Jul 2, 11:38 am, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 2, 2008 at 7:17 AM, Arien <[EMAIL PROTECTED]> wrote:
>
> > Can we get back
make the phone field have its own form.
(you can have multiple django forms in the same html form)
create a function that checks the country in the other form, and
returns a form that is either US or International base phone checking.
default it to one or the other, so that something shows up to s
i would use it as well.
i was actually thinking how on earth could i simplify the same thing i
do for every single project
(splitting settings.py to allow for revision control, splitting
urls.py, etc.)
On May 27, 8:30 am, "Valts Mazurs" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> This one sounds like a
another gigantic +1
On May 26, 8:51 am, rcs_comp <[EMAIL PROTECTED]> wrote:
> On May 26, 6:27 am, Jonas Pfeil <[EMAIL PROTECTED]> wrote:
>
> > Also not Django specific but support for Markdown Extra would be super-
> > cool:
>
> >http://michelf.com/projects/php-markdown/extra/
>
> Big +1!
--~--~-
i like the filter idea, but would prefer the default to be required,
and a filter to specify when something is not required (that might be
harder to push because of backwards incompatability)
i dont agree with the setting to be based on debug.
last thing i want is my test behavior being different
whats wrong with overridng save, then calling the super.save() ?
On May 2, 8:10 am, Alen Ribic <[EMAIL PROTECTED]> wrote:
> At the moment, it doesn't seem that a developers can do pre-save/post-
> save work cleanly when dealing with Forms in NewForms Admin using
> django.newforms.models.ModelForm
