This answers your question
http://djangoadvent.com/1.2/history-model-validation/
On Feb 19, 7:36 am, orokusaki wrote:
> BTW, I am aware of the ability to create your own custom model field
> class with a custom `validate()` method like my following example. I'm
> also aware of using a model's cl
Congratulations to all the developers who worked on 1.2, it's a
fabulous release.
P.S. It's sad but I'm almost as excited by the dropping of python 2.3
as I am the real features. Almost.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To p
+1 on Option 2.
I have written a basic deployment app (not quite ready for release
yet) that deploys a virtualenv for each version of your project,
roughly equivalent to Google App Engine. I specifically need to split
out the USER_MEDIA so that it isn't versioned. Internally if the
developer does
-1.
The only issue that I have with sites is that the default site should
be 127.0.0.1:8000 since that's what runserver defaults to. Putting
example.com as SITE_ID 1 only makes novice django developers shout and
throw things because like me they 'add 127.0.0.1:8000 and delete
example.com' instead
Ok yes seems like a slam dunk.. hell how about an --install-media for
python setup.py install ;)
On Jun 3, 10:18 pm, Jannis Leidel wrote:
> Am 30.05.2010 um 05:54 schrieb BrettH:
>
> > +1 on Option 2.
>
> > I have written a basic deployment app (not quite ready for release
