On 3/15/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> On 3/15/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> >
> > Thanks for pointing this out. django.parts appears to have been
> > removed while I was on vacation. I'm investigating.
>
> I removed django.parts after moving it's contents to
On 3/15/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> Thanks for pointing this out. django.parts appears to have been
> removed while I was on vacation. I'm investigating.
I removed django.parts after moving it's contents to
django.contrib.auth. However, django.parts.media was removed long
b
On 3/15/06, Jeremy Jones <[EMAIL PROTECTED]> wrote:
> I'm reworking a simple store with the magic removal branch
> and running into a bit of a snag. When I create a record in the admin
> interface for a model which has an ImageField, I get an import error in
> admin_list.py on ``from django.parts.
+1 for {# #} for me too.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email
scum wrote:
> +1 for {# #} comment tag. I've written some middleware to allow me to
> use the {# #} syntax and it has made templating much smoother.
>
> The {# #} middleware and other arguments on this subject can be found
> here:
> http://groups.google.com/group/django-developers/browse_frm/thr
Jacob Kaplan-Moss wrote:
>
> There isn't actually anything that Django's doing to "prevent" you
> here; it's an issue with the way python handles imports and
> PYTHONPATH. Think about it: if you've got a structure that looks like::
>
> todo/
> settings.py
> todo
On 3/14/06, Max Battcher <[EMAIL PROTECTED]> wrote:
>
> Joseph Kocherhans wrote:
> > On 3/14/06, Max Battcher <[EMAIL PROTECTED]> wrote:
> >> -1. I don't want to add layer after layer of code to my views to
> >> support whatever authentication backends I feel necessary.
> >
> > You don't have to.
> On 3/15/06, Christopher Lenz <[EMAIL PROTECTED]> wrote:
>> I definitely agree that the model layer should do validation, as long
>> as that doesn't mean it's the *only* layer that does validation
>> (that's not how I understood the proposal, but some some of the
>> comments seemed to imply that)
Adrian Holovaty wrote:
> On 3/15/06, Christopher Lenz <[EMAIL PROTECTED]> wrote:
>> Example: the string representation of a date in may depend on the
>> locale of the remote user, which the model knows nothing about. The
>> conversion from string to datetime will need to happen in a layer
>> that
On 3/15/06, Christopher Lenz <[EMAIL PROTECTED]> wrote:
> I definitely agree that the model layer should do validation, as long
> as that doesn't mean it's the *only* layer that does validation
> (that's not how I understood the proposal, but some some of the
> comments seemed to imply that). I ma
On Mar 15, 2006, at 8:15 AM, wsongkran wrote:
> I think django should not prohibit developer to name their application
> after their project name. Should I report this as bug?
There isn't actually anything that Django's doing to "prevent" you
here; it's an issue with the way python handles imp
Hi
When I create application with the same name as project like this
# django-admin.py startproject todo
# cd todo
# python manage.py startapp todo
# python manage.py runserver
Traceback (most recent call last):
File "manage.py", line 11, in ?
execute_manager(settings)
File "/usr/lib/pyt
+1 for {# #} comment tag. I've written some middleware to allow me to
use the {# #} syntax and it has made templating much smoother.
The {# #} middleware and other arguments on this subject can be found
here:
http://groups.google.com/group/django-developers/browse_frm/thread/d4e30079153011e1/55d
Am 15.03.2006 um 07:39 schrieb Russell Keith-Magee:
> Addressing the arguments against::
> 1) Validation shouldn't be in the model
>
> If validation isn't in the model, then the model is little more
> than a light data container; if all you have is a light data
> container, then the onus is on
Sorry for cross-posting, but I thought this would be relevant for
both groups. I'm reworking a simple store with the magic removal branch
and running into a bit of a snag. When I create a record in the admin
interface for a model which has an ImageField, I get an import error in
admin_list.py on
15 matches
Mail list logo
