If it's so difficult, why don't we start with a solution that solves
the problem for almost everyone. If someone encounters characters we
didn't think of, we can always add it to the mapping table...
Rudolph
--~--~-~--~~~---~--~~
You receiv
as I know. The sub-optimal alternative is using a foreignkey to the
User model, use inline editing and set max_num_in_admin to 1.
BTW when can we expect model inheritance? (I'm not asking for a date,
it's ready when it's done. But is it a high priority or
ther countries.
I agree with Bryan that all personal user information should be in the
profile model.
Rudolph
When looking to firstname / lastname from an international point of view
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
(not
DRY). At the moment I do it like this:
from django.utils.html import strip_tags
fields = ('address', 'city')
for field in fields:
self.__dict__[field] = strip_tags(self.__dict__[field])
Maybe the CharField and TextField could have a strip_tags optio
he idea of globally enabled escaping, and only do
it per template as described above. I'm not sure what I like the most.
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
Hi,
Derek Anderson mentioned the need for different kinds of escaping. So
maybe the syntax should be more something like:
{% autoescape xml on %}
and
{% autoescape javascript on %}
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are
Hi,
How about adding a command to django-admin.py that scans all the
templates of the project and enabled apps and gives you a list of
templates that have unescaped values in them, maybe even display the
tags/lines concerned. IMHO this could be very valueable info for a
developer.
Rudolph
Hi,
When I limit the choices in a one-to-many field with
"limit_choices_to", then the "list_filter" in the admin interface
should show the same limited choices. Does anyone disagree with this?
Else I file a feature requ
t). Does anyone else experience this since changeset
4500?
Rudolph
--~--~-~--~~~---~--~~
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@googlegroup
On Feb 15, 10:53 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Thu, 2007-02-15 at 06:02 -0800, Rudolph wrote:
> > Hi,
>
> > I think I found a bug introduced in changeset 4500 (http://
> > code.djangoproject.com/changeset/4500). When a min_num_in_ad
27;t correctly
> handling min_num_in_admin > num_in_admin cases prior to r4500.
>
> Regards,
> Malcolm
Thanks, I'll test my problem and let you know the result.
Regards,
Rudolph
--~--~-~--~~~---~--~~
You received this message because you
s are even deprecated in the near future:
http://www.python.org/dev/peps/pep-0328/.
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
Hi,
The subject of this discussion should of course be "Relative or
absolute imports", sorry for the typo. The mentioned relative import
of util is just an example since other modules in newforms are
imported in a relative fashion too.
Thank
Hi,
If it's so stable since Pycon, why doesn't it get merged into trunk?
The trunk is not a release, but it's the first step towards a new
release. I'm just impatient :)
Rudolph
--
Release early, release often...
--~--~-~--~~~---~--~~
You r
Will django.parts.media get dropped in again soon? I would like it if
the ImageField fully works again.
Cheers,
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To po
For me the same, hitting refresh a couple of times creates more and
more of those '[local] idle in transaction' things.
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers&quo
MPM one uses
(worker, prefork etc) and depending on the settings for things like
MaxClients, ThreadsPerChild, ServerLimit etc. As I said I'm not an
expert on this subject but I think it's interesting information for
people setting up t
ptions get ignored or are invisible.
Solution, change:
django/contrib/admin/templates/admin/index.html
Put this line:
{{ app.name }}
above the for loop instead of inside it.
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
It could be solved by putting the django-admin stuff inside a tag with
a django-admin class. Then ".django-admin p" or ".django-admin
#content" will format only the admin stuff and not your site.
Rudolph
--~--~-~--~~~---~--~~
You received
Wow, you fixed this faster than light can travel ;-)
Thanks
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-
el does
have an 'Admin' class. Seems like a bug to me, does anyone else
experience this?
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this gro
Yes, I use syncdb all the time, but it would be nice if you could also
let it generate the SQL without executing it.
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
d maybe it should also be possible to include some custom XHTML above
the add/change form too. Anyway, such a thing would make it really easy
to customise the admin interface a bit.
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
suggestion, see
http://code.djangoproject.com/ticket/578 and
http://code.djangoproject.com/ticket/61. As you can see, this is an old
issue, still not solved (I can't see a passwordfield in M-R).
Rudolph
--~--~-~--~~~---~--~~
You received this message becaus
Hi,
It seems like the Javascript for a SlugField stopped working in the
current revision of M-R. Or is it me messing things up... Does anyone
else experience this?
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
It's working again, the fault must have been on my side.
Rudolph
--~--~-~--~~~---~--~~
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@g
s
I do not have a fix (yet).
Rudolph
--~--~-~--~~~---~--~~
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 th
ation: it's not very attractive to create an empty app just to have
a place to put the taglibrary (this is what the doc's tell you). On the
other hand, I don't have a better solution (yet).
Rudolph
--~--~-~--~~~---~--~~
You received this message becaus
I just thought of a better solution. Taglibraries are just like
templates:
- they get loaded from paths set in settings.py
- and else they get loaded by the template_loaders
IMHO we could do the same thing for taglibraries.
Rudolph
--~--~-~--~~~---~--~~
You
lank = True,
)
birthday = models.DateField(
'birthday',
)
class Admin:
pass
Cheers,
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To p
request with tests and documentation:
https://github.com/django/django/pull/3550, could someone who has been
working on the new SecurityMiddleware review this pull request? The related
ticket is over here: https://code.djangoproject.com/ticket/15727
Thanks!
Rudolph
--
You received this message
, but that can be done by a little script.
Rudolph
On Jun 23, 12:28 pm, Jason Davies <[EMAIL PROTECTED]> wrote:
> Dear all,
>
> I have several clients who make heavy use of MEDIA_URL for styling
> their sites. The pages generated by the default 500 error handler
> look rather
y and would be
happy to contribute it. The nice thing is that HOTP has been studied
and at the moment can be considered safe.
Thanks, Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers"
uot;is_required" on the other
fields enforces that it gets a value. So to my opinion the is_required
attribute now has two meanings, which is a bad thing.
Thanks,
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goog
on-integer primary key.
Shall I add a ticket for this and add a patch for the documentation to
include such a remark?
Thanks!
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
T
cket that adds this
requirement to the docs:
http://code.djangoproject.com/ticket/7785
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to djang
Yes, that's why the proposed patch for the documentation says that
both must be of the same type:
http://code.djangoproject.com/attachment/ticket/7785/note-about-primary-keys.diff
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subsc
Wow, thanks for all the hard work to everyone involved! This is really
awesome!
I'll update the Dutch translations soon. And I'll have to start
preparing my company's 30+ Django projects for this change... ;)
Rudolph
--~--~-~--~~~---~--~~
Yo
e
bracket). I'd like propose to change back to milestone "1.0".
BTW thanks for al the amazing work being done for 1.0 release!
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django devel
Hi,
The process is documented here:
http://www.djangoproject.com/documentation/contributing/#submitting-and-maintaining-translations
Doing it right now is a good time since strings are frozen until 1.0
releases.
Rudolph
--~--~-~--~~~---~--~~
You received this
Here's to the most fabulous webframework in the world!
Rudolph Froger
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to dj
is to True. People would then need to
explicitly turn off CSRF protection globally or on a per form basis.
Thanks, Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to th
be used
in AJAX or forms generated by javascript:
var token = '{% csrf_token %}';
Cheers,
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post t
-developer
friendly to not escape {{ block.super }} by default.
Kind regards,
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email
Structured markup can only represent tree like organised objects
(without tricks). Maybe we can keep the primary keys inside the
fixtures, but add an optional attribute that indicates that the
primary key for this object is only used to link the objects together
when importing the data?
--~--~
rking with a pk=null (found this in the tests for the
serializers).
My suggestion:
It would be nice to use the django-admin.py with an extra option to
dump certain data without primary keys. If you like the idea, I'll
file a ticket (and maybe implement it at the upcoming Django sprint).
Re
46 matches
Mail list logo