Thanks, appreciate it
--~--~-~--~~~---~--~~
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 to
Hi
I have been using it, and I have found a few bugs. Some posted some
not. An example would be the limit_choices_to. But Luke fixed it almost
stragith away.
There is also every changing landscape, just take a look at the commit
log. http://code.djangoproject.com/log/
The point is to develop an
Hi
I am very interested in starting aproject at my company in Django, but
am not keen on starting one of 0.91. So I am hoping the MR will be
merged soon too :-)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djan
Hi
I think I have found a bug in the MR branch with verbose name.
According the (out of date) documentation verbose_name_plural will use
verbose_name + 's'.
However when I just set verbose_name, Admin still shows the wrong name.
If I set the verbose_name_plural, it works.
Example:
Class TelDir
This is a common thread :-) and one I am interested in, but you can
search the forumn for the results. Bascially it will be done when its
done it seems :-)
S
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
>However, I don't like it if it's going to be introduced as a scaling
>solution; I'd rather have the various tiers of infrastructure (load
>balancing at the front, application in the middle, database in the
>back) remain as loosely coupled as possible.
Absolutly, scaling is the last reason to int
+2 on the idea of supporting multiple backends. Its a huge feature gap
which effects usability of the framework quiet severly. As for the
"how" I think it needs some very carefull thought as the current django
model is the global settings file it would have to have multiple setups
in there, and po
I used it on several examples and in each case it worked.
--~--~-~--~~~---~--~~
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 unsubsc
Your patch seems to be work.
--~--~-~--~~~---~--~~
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 em
I am +1 on the idea of a feature freeze and was going to make a
seperate post on this idea but read this post first.
I think there is a lot of good stuff in MR now, and a move towards
getting a stable version 0.92 with these features would be brilliant.
Naturalyl I want all the future proposed
On the Ticket.
--~--~-~--~~~---~--~~
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 to [EMAIL
Hi
As far as I know I dont access request.user. But I still got the error
which is why I asked about it being required. I do have session
middleware installed, so I am guessing that session middleware accesses
request.user then ?
Thanks,
C
--~--~-~--~~~---~--~---
Hi
This worked. I take it Request User Middleware is now always required ?
--~--~-~--~~~---~--~~
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@googlegro
Thbanks for the reply, will try it out.
--~--~-~--~~~---~--~~
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 gro
Hi
Added an attempt at Tut 4
--~--~-~--~~~---~--~~
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 e
Hello,
I just updated my MR branch and am getting the following error:
Request Method: GET
Request URL:http://127.0.0.1:8000/surveys/question/list/
Exception Type: AttributeError
Exception Value:'WSGIRequest' object has no attribute '_user_source'
Exception Location:
Thanks,
thats very informative.
--~--~-~--~~~---~--~~
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, se
Also one more point, which Tom did point out. This is a use it if you
want it feature. If you like generic names this wont change anythign
your currently doing.
So you increasing the flexibility of Django. Giving more features not
less.
--~--~-~--~~~---~--~~
You
I can see how on occasion you might swap out one template for another,
but its more a rarity (in my experience). I agree with Luke, in that
templates are alsmot always specific. Why not help make them more
readable and easier to use?
If you go along with the idea that template designers are not c
Yes
Generic VIEWS. Where does the word veiw imply template? The view is
generic the template is specific. My proposal is make the views even
more generic and templates even more usefull.
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
Hi
I realise this is still in the early stages of development, but I had
one question on performance. Have you done any performance comparisons
with django's template system?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Hi
I have raised the following ticket:
http://code.djangoproject.com/ticket/1399
I propose adding a new paramter to the list_detail.py generic view to
allow you to name your model/objects to something other than 'object'
or 'object_list'.
I prospose and feel that more meaning names make templat
Hi
I have been thinking about doing something like this, and it seems you
probably would have to use the new save() method. However you would
still need a model for each history table. Although I was toying with a
genric history table (more akin to a log) where you could then easly
code it up onc
Hi
I am using manage.py from /manage.py
Can you send me an examlpe model file ? I would just like to make sure
it nothing do with my typing.
Thanks,
S
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django de
Hi
I hope this is the correct place.
I just took downloaded the magic removal branch, and entered some
models in the new way.
manage.py sql* functions dont seem to work.
if i run the manage.py shell, and import manually it appears to work,
but manage.py sql or sqlall or install, just error.
I
25 matches
Mail list logo
