Re: Ping for ticket #6095 (m2m intermediary model)
Hello, Thanks for the responses guys! Have fun with your holiday celebrations. -Eric Florenzano On Dec 21, 9:49 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On Dec 22, 2007 6:48 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > Hello All, > > > I've been working on adding m2m intermediary model functionality for a > > while now, and the patch is to the point where I can't seem to find > > any more edge cases to address. At this point it needs people to try > > it out and/or review the code. There are up-to-date tests and > > documentation to go along with the patch, by the way. > > > The files to look at are 6095-alpha-05.diff, and docs.diff. > > > I know that everyone's busy, but I just wanted to bring this up on- > > list to raise awareness. > > Hi Eric, > > I've been keeping an eye on this patch, but I haven't had a chance for > a week or so, what with the general pre-Christmas rush. I'll see if I > can find some time to take the patch for a spin, but it could be about > a week or so before that happens. > > Yours, > Russ Magee %-) --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Ping for ticket #6095 (m2m intermediary model)
Hey Eric -- Yeah, I've been keeping an eye on your work; looks pretty nice! I'm on my way to my parents' house for the holidays, so the chance of me actually doing anything with your patch soon is pretty low, but I'll do my best to get to it as soon as I get back. Thanks! Jacob --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Reconsider ADMIN_MEDIA_PREFIX default?
Guys, this is really degenerating into a bikeshed issue. Let it rest for a while, OK? Endless "me too" comments don't add anything useful to the discussion, and there are larger and more important things to be working on right now. And if anybody feels the need to post a snarky comment about perfectionists caring about little details, I'd like to remind them that perfectionism is, in large part, about knowing how to prioritize: getting the little details right while larger problems persist is not something a "perfectionist" would accept. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Reconsider ADMIN_MEDIA_PREFIX default?
On Dec 21, 2007 4:42 AM, Robert Šmol <[EMAIL PROTECTED]> wrote: > As my 0.02 cents of new comer I can confirm this was one of the things > that slows adoption of Django. Proposed change to have ADMIN_MEDIA_PREFIX to > be /admin_media/ (or either /media/admin/ ) makes more sense (at least for > me). When I started with django I was confused with when I used /media for > my media (as suggested in doc) just to find out my admin section is not > working properly anymore. I either copy the admin folder from django installation folder> to /media or I now change ADMIN_MEDIA_PREFIX to > be /admin_media/ and setup a static server in my urls.conf and I'm pretty > sure this not the right way anyway (it works but not out of the box). > I also had some issues with this when I first started learning Django. I remember following through the tutorials only to find that media wasn't working as I had expected. The problem was solved after visiting the IRC channel and receiving some sarcastic support from someone in there. I consider myself proficient with Django now, so this is not a problem, although one of the first things I do when I start a new Django app is change ADMIN_MEDIA_PREFIX to 'admin-media'. If this thread still means anything to the django devs, I am +1 on it. To me it seems like a minor backwards-incompatible change that would result in a more enjoyable experience for Django newcomers and it might as well be cleared up in the next major release. --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Reconsider ADMIN_MEDIA_PREFIX default?
As my 0.02 cents of new comer I can confirm this was one of the things that slows adoption of Django. Proposed change to have ADMIN_MEDIA_PREFIX to be /admin_media/ (or either /media/admin/ ) makes more sense (at least for me). When I started with django I was confused with when I used /media for my media (as suggested in doc) just to find out my admin section is not working properly anymore. I either copy the admin folder from to /media or I now change ADMIN_MEDIA_PREFIX to be /admin_media/ and setup a static server in my urls.conf and I'm pretty sure this not the right way anyway (it works but not out of the box). Than I had to disturb people in IRC and mailing lists and I'm pretty sure a lot of newcomers do the same. And since you promote DJANGO to be easy to use you have to expect really newcomers with hardly any Apache, project folder organization, mod_python experience at all. Not gurus like you are, for whom this seems such a trivial change to not even bother with it. This is when I find Yuris comment about not understanding your users requirements to be correct and valid. Although I like Django very much I really cannot understand why there is such a lot of everyones effort wasted on such a small and clean up or cosmetic (remember django fav icon issue?) changes instead of just doing them. I use 0.96 and I'm pretty sure the SVN code is already a lot of backward incompatible right? all the best --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
