Re: mod_python documentation issues
Hi, sorry to step in. I'm newcomer to Django+Python. > Except that you do /not/ need to add the project directory to > > pythonpath, if you just reference everything properly and include the > > project name. I have run into exactly this issue and spend couple of hours searching django users archives (maybe even whole day). When you know python for some time it is quite obvious that either include every project dir on PYTHON path or use full naming. However not as newbie, specially when you follow the URL tutorial part for first time you can get the feeling like python always check even current directory. So you end up with various mixed import strings across your first application, bit thinking that this is probably the way how to de-couple apps from projects and it works on django testserver. I agree some small documentation update would fix it. best regards robert --~--~-~--~~~---~--~~ 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: Still no favicon - Re: Visual recognition of Django website
Hello all, I'm the creator of this mess as I'm the issuer of the ticket 3867. I like django very much, I'm not that great at python yet to contribute so that was my try to help you guys. If I would only know how much time would be wasted on this discussion I wouldn't raise that call at all. So sorry for that. Still, I have to say I miss the favicon a lot: http://www.stereoit.com/django/django_favicon_missing.png and I thought it is just about taking the icon file and place it to the root of the htdocs folder (1 minute?). I've attached another try of django favicon to the ticket (16x16,48x48 and GIMP xcf file), this time with "dj" that clearly distinguish django. Any comments on the icon style is appreciated and I will improve it to the point where you like it. Once everybody is happy with that, just place it to the htdocs and move on. I hope I didn't offended anyone. I know you all are really busy with django internals. Kind regards, Robert Smol --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: mod_python issue
Maybe django-developers is really confusing ("I am developer using django"
is not "I am developer of the django" ), have you been guys thinking about
moving to another name? django-internals?
On Sun, Apr 13, 2008 at 9:28 PM, Mike Scott <[EMAIL PROTECTED]> wrote:
> This mailing list is for the development of django itself. Your issue is
> with mod_python and is probably better answered at
> http://mailman.modpython.org/mailman/listinfo/mod_python
>
> It has nothing to do with django itself.
>
>
>
>
> If you have any issues with django, then the first port of call (and often
> the only port of call) is the django-users list.
>
> Cheers.
>
>
> On Mon, Apr 14, 2008 at 6:24 AM, jurian <[EMAIL PROTECTED]> wrote:
>
> >
> > I've been battling with this issue for half a day now.
> >
> > This is the error I'm getting when starting-up apache:
> >
> > [Sun Apr 13 20:13:29 2008] [error] make_obcallback: could not import
> > mod_python.apache.\n
> > Traceback (most recent call last):
> > File "/home/django/active/Python-2.5.2/lib/python2.5/site-packages/
> > mod_python/apache.py", line 23, in
> >import time
> > ImportError: No module named time
> > [Sun Apr 13 20:13:29 2008] [error] make_obcallback: Python path being
> > used "['/home/django/active/Python-2.5.2/lib/python25.zip', '/home/
> > django/active/Python-2.5.2/lib/python2.5', '/home/django/active/
> > Python-2.5.2/lib/python2.5/plat-linux2', '/home/django/active/
> > Python-2.5.2/lib/python2.5/lib-tk', '/usr/lib/python2.5/lib-dynload',
> > '/home/django/active/Python-2.5.2/lib/python2.5/site-packages', '/usr/
> > lib/python2.5/site-packages']".
> >
> >
> > The server works, but mod_python doesn't.
> >
> >
> >
> >
>
> >
>
--~--~-~--~~~---~--~~
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: mod_python issue
Ok, so you mean people post here even the read the description? I was more
thinking that they read only the group-name, not the description of the
group name and this is what is causing their confusion. Anyway, I guess not
a big deal.
On Sun, Apr 13, 2008 at 10:54 PM, Jacob Kaplan-Moss <
[EMAIL PROTECTED]> wrote:
>
> On Sun, Apr 13, 2008 at 2:10 PM, Robert Šmol <[EMAIL PROTECTED]>
> wrote:
> > Maybe django-developers is really confusing ("I am developer using
> django"
> > is not "I am developer of the django" ), have you been guys thinking
> about
> > moving to another name? django-internals?
>
> The description of the list
> (http://groups.google.com/group/django-developers/about) says:
>
> """
> Discussion group for Django developers. This group is used for
> discussion of developing Django itself, not user questions; Please use
> django-users for issues regarding using the framework, questions for
> the Django user community outreach, etc.
> """
>
> Changing the name would just give folks another thing to ignore.
>
> 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
-~--~~~~--~~--~--~---
