Re: lost admin on upgrade to django 1.3
Actually I'm not using virtualenv, I just installed the new version on my mac tar xzvf Django-1.3.tar.gz cd Django-1.3 sudo python setup.py install and it overwrote the older version in python/2.6/site-packages/django (I have 1.1 running on my notebook, that's how I checked where the damn admin templates directory was) I'm just going to quit my project and reinstall and see what happens. Maybe I'll install python 2.7 but it's late... Thanks for the confirmation that I should indeed have that directory. Wendy -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/yB-1Z3mjbvIJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: lost admin on upgrade to django 1.3
I'm using Django 1.3, and the templates exist in site-packages. Within my virtualenv: lib/python2.7/site-packages/django/contrib/admin/templates/admin/login.html How did you install/upgrade 1.3? Are you using virtualenv? Do you have multiple versions of Python on your system? Try just creating a fresh virtualenv using the --no-site-packages option and pip install Django and see if your project will work that way. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: lost admin on upgrade to django 1.3
No, I haven't. I think it has to do with the way the admin templates are loaded. I do notice that in my django 1.1 install there is an existing templates directory in site-packages/django/contrib/admin but in my 1.3 install there is no templates directory. So I think that's the problem, I'm trying to wrap my head around how to refer to the admin templates, like where the heck are they in this version? Have they gone missing in the install (mac 10.6.8)? Or are they someplace totally different? Does that make sense? Thanks, Wendy -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/_BV8nyWuFGAJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Mysterious Path Issue Django & Apache
I think I'm adding the directories to sys.path correctly. For example, in my wsgi file, this works: path = '/home/devon/django-projects/' if path not in sys.path: sys.path.append(path) ...but if I change the path value like this, then Apache gives a 500 server error: path = '/home/devon/code/dj/' if path not in sys.path: sys.path.append(path) ...both directories exist, and I've started Django projects in each (both with the same name so I don't have to change the value I pass into os.environ['DJANGO_SETTINGS_MODULE'] -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: lost admin on upgrade to django 1.3
Could it have something to do with staticfiles? Have you started using any new middleware or contrib apps? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: about django
@ bruno desthuilliers, Thank you. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Django Memory hosting issues?
**EDIT** sorry, just another question, Is it possible to point two domain names to the same application? Its sort of tough to explain. In webfaction, It allows me to make an application through the control panel, and I can link a domain to it. Inside this application, I can create actual django applications. Can I link one domain to one of those applications, and another domain to another one of those applications? On Jul 29, 9:29 pm, rajwrote: > Hey guys, > Just need some advice. I currently have a webfaction account, and It > gives me 80mb of space. But I didn't know that each django application > takes up approximately 40mb (ran over the limit without realizing it), > so I can make only a max of 2 different websites. If I want to have > the ability to make as many websites as I want, what would you guys > recommend? Adding on additional memory costs too much money. I was > looking into cloud hosting, but that is really expensive starting off. > If necessary, I would switch to that. Does cloud hosting allow this > type of memory flexability? Do you guys know any cheap cloud hosting, > or a better idea for hosting? Thank you. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Django Memory hosting issues?
Hey guys, Just need some advice. I currently have a webfaction account, and It gives me 80mb of space. But I didn't know that each django application takes up approximately 40mb (ran over the limit without realizing it), so I can make only a max of 2 different websites. If I want to have the ability to make as many websites as I want, what would you guys recommend? Adding on additional memory costs too much money. I was looking into cloud hosting, but that is really expensive starting off. If necessary, I would switch to that. Does cloud hosting allow this type of memory flexability? Do you guys know any cheap cloud hosting, or a better idea for hosting? Thank you. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
lost admin on upgrade to django 1.3
Hello, I just upgraded to 1.3 and thought all was well until I tried to access LOCALHOST/admin/ Can anyone tell me why I'm getting this exception Exception Type: TemplateDoesNotExist Exception Value: admin/login.html ? Was working fine in the older version. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/2iEDmZQCEtYJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Humanizing decimals in templates
Hi. The humanize module - https://docs.djangoproject.com/en/1.3/ref/contrib/humanize/ does not support humanizing decimal values similar to 'intcomma', only integers. Is there an extension to do so, and if not how would one write one? How would one use this http://djangosnippets.org/snippets/842/ with a template? Thanks. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
On Fri, Jul 29, 2011 at 6:14 PM, Jacob Kaplan-Mosswrote: > Hi Bobby -- > > I'm quite sorry if you took my words as a threat. Such wasn't my > intent -- at all. I'm simply trying to make clear certain community > expectations. You're completely right that banning would be wildly > inappropriate, and I certainly wasn't suggesting that. > > The Django community has historically been known as a friendly, > accepting, professional one free of the usual flamewars that crop up > on free software. I really appreciate your help in keeping it that > way. I think we can all agree that a helpful, welcoming community is > something to be proud of. > Actually, Jacob does have a point. This is pretty much the only list I *enjoy* being a part of, and it probably wouldn't be like this unless certain etiquette was enforced. > > That's the last I've got to say on the matter; at this point we're > basically going in circles. I hope I made my point clear enough. If > not, please feel free to contact me off-list so everyone else can get > back to talking about software. > > Thanks! > > Jacob > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
On Fri, Jul 29, 2011 at 6:14 PM, Jacob Kaplan-Mosswrote: > Hi Bobby -- > > I'm quite sorry if you took my words as a threat. Such wasn't my > intent -- at all. I'm simply trying to make clear certain community > expectations. You're completely right that banning would be wildly > inappropriate, and I certainly wasn't suggesting that. > > The Django community has historically been known as a friendly, > accepting, professional one free of the usual flamewars that crop up > on free software. I really appreciate your help in keeping it that > way. I think we can all agree that a helpful, welcoming community is > something to be proud of. > Actually, Jacob does have a point. This is pretty much the only list I *enjoy* being a part of, and it probably wouldn't be like this unless certain etiquette was enforced. > > That's the last I've got to say on the matter; at this point we're > basically going in circles. I hope I made my point clear enough. If > not, please feel free to contact me off-list so everyone else can get > back to talking about software. > > Thanks! > > Jacob > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
Just for the record, this topic was also posted on the Satchmo list and there are some decent performance improvement related discussions. No doubt there are configurations of Satchmo that result in less than desirable speed but there are some real life comments/examples from folks running big stores. Hopefully that will be useful to others that stumble upon this thread and are looking for some ideas on how to improve performance. Thanks, Chris -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/qYv3LCUZVFwJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Mysterious Path Issue Django & Apache
Check if the base directory is added in you current python path when running from wsgi Putting a line like "print >> sys.stderr, sys.path" in your wsgi file right after the initial import should let you verify that. On Sat, Jul 30, 2011 at 1:25 AM, Devon Youngwrote: > I apologize in advance if this is actually a stupid question, but I'm > thoroughly stumped since yesterday about this. > > First, it should be noted I come from a PHP background with a little > experience in Perl, and I'm learning Python since Sunday. Also, I'm > using: > > Python 2.7 > Apache 2 (with mod_wsgi) > Django 1.3 > Ubuntu 11.04 > > Ok now... I had django workin' perfectly, and then decided I wanted to > move the folder I was keeping my projects & apps in. So I deleted that > folder and made a new one, intending to begin over. At that time, I > also updated the path in the .wsgi file. > > All runs fine when I run it as python manage.py runserver, but Apache > now gives me a 500 server error, which in the error.log says > "ImportError: Could not import settings 'combs.settings' (Is it on > sys.path?): No module named movies.settings". Even though the path to > the movies project is completely correct in the .wsgi file. > > I've been trying to debug this since yesterday, and just today I > figured out that if I remake the original folder & move my project > there & update the path in .wsgi ... then Apache is happy with it. > > I cannot make sense of this. Do I need to uninstall Django & then > reinstall it from scratch? I doubt it's a permissions problem, 'cause > I remade the directory & didn't chmod it differently. Did I have to > hard code something during install that I've forgotten about since? My > head is spinning with all these things to do to keep Django working > that I can't remember half of what I did... altho, when I look back on > the instructions I followed, I can't see anywhere that would get me to > make a hard link or anything. > > Does anyone know how I can fix this so I can keep my projects in the > folder I want to keep them? > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Mysterious Path Issue Django & Apache
It's your PYTHONPATH environment variable. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Mysterious Path Issue Django & Apache
I apologize in advance if this is actually a stupid question, but I'm thoroughly stumped since yesterday about this. First, it should be noted I come from a PHP background with a little experience in Perl, and I'm learning Python since Sunday. Also, I'm using: Python 2.7 Apache 2 (with mod_wsgi) Django 1.3 Ubuntu 11.04 Ok now... I had django workin' perfectly, and then decided I wanted to move the folder I was keeping my projects & apps in. So I deleted that folder and made a new one, intending to begin over. At that time, I also updated the path in the .wsgi file. All runs fine when I run it as python manage.py runserver, but Apache now gives me a 500 server error, which in the error.log says "ImportError: Could not import settings 'combs.settings' (Is it on sys.path?): No module named movies.settings". Even though the path to the movies project is completely correct in the .wsgi file. I've been trying to debug this since yesterday, and just today I figured out that if I remake the original folder & move my project there & update the path in .wsgi ... then Apache is happy with it. I cannot make sense of this. Do I need to uninstall Django & then reinstall it from scratch? I doubt it's a permissions problem, 'cause I remade the directory & didn't chmod it differently. Did I have to hard code something during install that I've forgotten about since? My head is spinning with all these things to do to keep Django working that I can't remember half of what I did... altho, when I look back on the instructions I followed, I can't see anywhere that would get me to make a hard link or anything. Does anyone know how I can fix this so I can keep my projects in the folder I want to keep them? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Django + PyPy = ?
OK. Try: $ cd /to/whereever/manage.py/is $ /home/wsgi/pypy-1.5/bin/pypy ... import sys, pprint pprint.pprint(sys.path) Are the directories holding your django install there? If not, are the directories here pretty much only within (I'm guessing) /home/wsgi/pypy-1.5/lib ? That is, the stuff that you've used easy_install or pip install to install, or python setup.py to install, may be installed in your python's lib directories, but pypy may not be falling back to use those when it doesn't find them in its own lib dirs (I don't know if it is supposed to). If this seems to be the problem, you have a number of options available, including using pypy to run ez_setup.py to get an easy_install that installs there, and reinstalling stuff using that easy_install, or getting packages from pypi and running their setup.py files by hand using pypy. But before you go to far, find one simple package that you have installed, something without a lot of dependencies, in your python, that you can't import from the pypy prompt, and see what it takes to install that for pypy. Bill On Fri, Jul 29, 2011 at 1:37 PM, Dmitry Pisklovwrote: > Well, on the second step it fails: > In the different directory (not in bin dir): > $ /home/wsgi/pypy-1.5/bin/pypy > Python 2.7.1 (b590cf6de419, Apr 30 2011, 02:00:34) > [PyPy 1.5.0-alpha0 with GCC 4.4.3] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > And now for something completely different: ``"that's why the 'or' is really > an > 'and' "'' > > No error, as you can see... Now running shell: > $ /home/wsgi/pypy-1.5/bin/pypy manage.py shell > Traceback (most recent call last): > > > File "app_main.py", line 53, in run_toplevel > > > File "manage.py", line 2, in > > > from django.core.management import execute_manager > > > ImportError: No module named django.core > The same error... > PS: I'm using fastcgi behind nginx. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/iAijeg2ZUIsJ. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
Django is the best thing since the Civil Rights Movement. Satchmo is ok for the most part except for certain things which do not work unless you correct the errors in the programming. I'm sorry for ranting on the board. I will never rant again. @bloatedmanatee -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Django + PyPy = ?
Well, on the second step it fails: In the different directory (not in bin dir): $ /home/wsgi/pypy-1.5/bin/pypy Python 2.7.1 (b590cf6de419, Apr 30 2011, 02:00:34) [PyPy 1.5.0-alpha0 with GCC 4.4.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. And now for something completely different: ``"that's why the 'or' is really an 'and' "'' No error, as you can see... Now running shell: $ /home/wsgi/pypy-1.5/bin/pypy manage.py shell Traceback (most recent call last): File "app_main.py", line 53, in run_toplevel File "manage.py", line 2, in from django.core.management import execute_manager ImportError: No module named django.core The same error... PS: I'm using fastcgi behind nginx. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/iAijeg2ZUIsJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
Django is the next best thing to Emancipation. I like Satchmo for the most part. I'll keep my rants off list. . I promise. You can follow me on twitter @bloatedmanatee from now on. Thanks for setting me straight everyone! On Jul 29, 1:14 pm, Jacob Kaplan-Mosswrote: > Hi Bobby -- > > I'm quite sorry if you took my words as a threat. Such wasn't my > intent -- at all. I'm simply trying to make clear certain community > expectations. You're completely right that banning would be wildly > inappropriate, and I certainly wasn't suggesting that. > > The Django community has historically been known as a friendly, > accepting, professional one free of the usual flamewars that crop up > on free software. I really appreciate your help in keeping it that > way. I think we can all agree that a helpful, welcoming community is > something to be proud of. > > That's the last I've got to say on the matter; at this point we're > basically going in circles. I hope I made my point clear enough. If > not, please feel free to contact me off-list so everyone else can get > back to talking about software. > > Thanks! > > Jacob -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
Hi Bobby -- I'm quite sorry if you took my words as a threat. Such wasn't my intent -- at all. I'm simply trying to make clear certain community expectations. You're completely right that banning would be wildly inappropriate, and I certainly wasn't suggesting that. The Django community has historically been known as a friendly, accepting, professional one free of the usual flamewars that crop up on free software. I really appreciate your help in keeping it that way. I think we can all agree that a helpful, welcoming community is something to be proud of. That's the last I've got to say on the matter; at this point we're basically going in circles. I hope I made my point clear enough. If not, please feel free to contact me off-list so everyone else can get back to talking about software. Thanks! Jacob -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
On Fri, Jul 29, 2011 at 5:16 PM, Bobby Robertswrote: > opinions on software should never be taken personally and should never > be silenced. I take heat over programming on a daily basis just as I > have for the past 30 years. It's part of the business. Good > programmers take it, grow from it and come back with a better product. > > There was no slight intended toward the programmers and I doubt I'm > the only one that has ever said that this version is bloated or with > issues. I am sorry to the Satchmo team, and the sweet gentle aquatic > bovine Lmao. That just made my day. > If I have caused personal insult to either. I have used > Satchmo for over three years now and it's simply this version which I > believe perhaps was rushed. It seems to be behind the django > compatibility curve and some of the documentation is outdated as well > and not everything works as it should and needs serious tweaking to > the code to get it to even function. > > Boot me out if you feel I need to be booted from the group. However, > that would be the biggest flame to an open source board note > this is an opinion, i'm not meaning to insult ANYONE. > I don't think anyone should be kicked just for voicing their own opinion. How many times have we all said "omg X or Y is a bloated pos". How many times have we personally insulted many other products, such as Windows, Debian, Apache etc..? Whenever I build a new project, the first thing I do is show it to other developers which I trust, and ask for their honest opinion. They will quite often say to me "Cal, if you write code like this again, I will slap you". And it's this sort of advice which put me where I am today :) > > If i'm allowed to stay, perhaps I will use the new WC3 or > tags to make things clear. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
opinions on software should never be taken personally and should never be silenced. I take heat over programming on a daily basis just as I have for the past 30 years. It's part of the business. Good programmers take it, grow from it and come back with a better product. There was no slight intended toward the programmers and I doubt I'm the only one that has ever said that this version is bloated or with issues. I am sorry to the Satchmo team, and the sweet gentle aquatic bovine If I have caused personal insult to either. I have used Satchmo for over three years now and it's simply this version which I believe perhaps was rushed. It seems to be behind the django compatibility curve and some of the documentation is outdated as well and not everything works as it should and needs serious tweaking to the code to get it to even function. Boot me out if you feel I need to be booted from the group. However, that would be the biggest flame to an open source board note this is an opinion, i'm not meaning to insult ANYONE. If i'm allowed to stay, perhaps I will use the new WC3 or tags to make things clear. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
Personally, I don't see why this has caused such a fuss. It is quite obvious from OPs original message that it was a bit of light hearted humor. I think the most appropriate response here would be "loosen up..?" Cal On Fri, Jul 29, 2011 at 4:26 PM, Jacob Kaplan-Mosswrote: > On Thu, Jul 28, 2011 at 11:16 AM, Cal Leeming [Simplicity Media Ltd] > wrote: > > Hold on, we are in danger of restricting the freedom of speech on this > > mailing list. > > There is no right to free speech on a mailing list. > > We already restrict what's allowed on this list. Beekeeping, wool > socks, hand grenades and a nearly infinite collection of topics are > declared off-topic. Similarly, we have certain community standards -- > politeness among them -- and we can and will enforce them. > > If you'd like to have an anything-goes forum where insults and flames > are tolerated then I encourage you to start your own. Around here, I > expect a certain level of decorum and I will enforce it. > > Jacob > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No module named servers.basehttp
I am following the tutorial. runserver ran fine until I added the admin feature. Now I enter D:\Python26\Lib\site-packages\django>d:\Python26\python mysite/manage.py runserver Traceback (most recent call last): File "mysite/manage.py", line 14, in execute_manager(settings) File "d:\Python26\lib\site-packages\django\core\management \__init__.py", line 438, in execute_manager utility.execute() File "d:\Python26\lib\site-packages\django\core\management \__init__.py", line 379, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "d:\Python26\lib\site-packages\django\core\management \__init__.py", line 261, in fetch_command klass = load_command_class(app_name, subcommand) File "d:\Python26\lib\site-packages\django\core\management \__init__.py", line 67, in load_command_class module = import_module('%s.management.commands.%s' % (app_name, name)) File "d:\Python26\lib\site-packages\django\utils\importlib.py", line 35, in import_module __import__(name) File "d:\Python26\lib\site-packages\django\contrib\staticfiles \management\commands\runserver.py", line 4, in from django.core.management.commands.runserver import BaseRunserverCommand File "d:\Python26\lib\site-packages\django\core\management\commands \runserver.py", line 9, in from django.core.servers.basehttp import AdminMediaHandler, run, WSGIServerException ImportError: No module named servers.basehttp How do I fix this? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
On 2011-07-29, at 01:26 , Russell Keith-Magee wrote: > Yes, it really was. He opened a request for a subject line and first > sentence by comparing Satchmo to a fat, ungainly animal. Now here I draw the line, this is not acceptable. Manatees have feelings too. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Satchmo, the bloated manatee
On Thu, Jul 28, 2011 at 11:16 AM, Cal Leeming [Simplicity Media Ltd]wrote: > Hold on, we are in danger of restricting the freedom of speech on this > mailing list. There is no right to free speech on a mailing list. We already restrict what's allowed on this list. Beekeeping, wool socks, hand grenades and a nearly infinite collection of topics are declared off-topic. Similarly, we have certain community standards -- politeness among them -- and we can and will enforce them. If you'd like to have an anything-goes forum where insults and flames are tolerated then I encourage you to start your own. Around here, I expect a certain level of decorum and I will enforce it. Jacob -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Cannot upload compressed zipfile
solved problem, method of joining buffer was corrupting data. you need to use something like buffer =''' for x in f.read(4096): buffer+=x the solution in django works. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/qaloUAJrKV4J. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
"This URL appears to be a broken link."
It seems that verify_exists=True as in URLField([verify_exists=True, max_length=200, **options]) has problems (1.3; 2.7). For example, this site is just fine http://www.rydex-sgi.com/ However, validation reports "This URL appears to be a broken link." This URL http://www.rydexsgi.com/ appears to be OK - in reality it is redirected to http://www.rydex-sgi.com/. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
[Commercial] Freelance developer looking for long-term/contract based work
Hi, I'm an experienced Django developer, with good experience in web application development using Django as the underlying backbone. Have done numerous projects in this, and my entire work experience is also build around it. Summary: I love to work on challenging Django/Python projects, which involves working and experimenting with new and interesting ideas and technologies. Fancy my chances to work on performance enhancements and optimizations of web applications, along with architectural designs of web products. Skillset: Web application development, Django/Python, GAE, jQuery, Facebook Application Development Links to some publicly available code snippets of mine: http://scratch-blog.appspot.com https://github.com/subhranath LinkedIn profile (Needs to update the projects section soon): http://in.linkedin.com/pub/subhranath-chunder/24/50/a01 Currently, I'm switching work from a full-time employee to a full-time freelancer. Thus, I'm looking for some nice and interesting long-term or contractual opportunity for work engagement. I could surely use some help to get some project, to get me started on my freelancer career. Please let me know if anyone is interested, or need any more details. Thanks, Subhranath Chunder. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Crop feature in django application
¿Why cropping on upload when you can let the system keep the center of attention centered? https://github.com/francescortiz/image On Jul 29, 10:50 am, jaspreet kaurwrote: > I want to add crop option in Django application > i followed the link:http://code.activestate.com/pypm/django-image-cropper/ > By following the steps given in the link, it doesnot give any effect > on application > Is there more steps to do for adding crop feature > Thanks > > -- > Jaspreet -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: about django
On Jul 29, 12:11 pm, jaspreet kaurwrote: > On Fri, Jul 29, 2011 at 8:51 AM, Phang Mulianto wrote: > > welcome to the club. ... > > start with the documentation like others said, then more deep buy a book for > > reference, then create a pilot project... > > Please tell me about pilot project. What is it? > Any project that's simple enough to be completed by a newbie BUT no simpler (that is, not the tutorial poll app). The point is that you have to be one your own with it (no copy-paste from a tutorial) and that you have to deal with the whole range of real-life problems. You will of course make a lot of mistakes and the implementation will very certainly suck, but if and when you complete it you should be ready to start working on a real project and have a change to deliver on time something that doesn't suck too much. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Django admin upload image to few folders
It's possible I'm a little slower this morning, so could you help me understand what you mean? What do you mean you want to use the index for the filename instead of the pk? On Jul 28, 7:36 pm, Jonathan of Cambridgewrote: > I've been working on using django-filetransfers. > > Curious whether it works well for you. > > My current challenge is that I want to use the index as the file name > for the url rather than the pk. Anyone have an idea how to do that > easily? > > I'm thinking this is a simple question about databases in django. > > Thank you in advance, > > Jonathan > --- > -- > > class UploadModel(models.Model): > file = models.FileField(upload_to='uploads/%Y/%m/%d/%H/%M/%S/') > > class UploadForm(forms.ModelForm): > class Meta: > model = UploadModel > > from filetransfers.api import serve_file > > def download_handler(request, pk): > upload = get_object_or_404(UploadModel, pk=pk) > return serve_file(request, upload.file) > > On Jul 23, 1:17 am, Vusal Alishov wrote: > > > > > > > > > Hello, I want to upload image in django-admin interface to few > > folders. > > My models image field such: image = > > models.ImageField(upload_to='images') > > How can I do it? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Implementing one app for multiple users with their own data.
On Fri, Jul 29, 2011 at 11:14 AM, mongoosewrote: > Hi, > > I've a web app which works nicely on a per user or per company basis. > However I've gotten to the point where I want to run multiple > companies through the same app(not have to redeploy for each client). > However each client needs their own data and shouldn't be able to see > other clients data. A DB per client is probably best but I'm not sure > how I go about implementing this. > > In theory I'd like each client to be able to: > -All log in at the same url. > -Each have their own DB and own admin user etc. > -All be running through the same web app. > > Do I need something like a master DB which will hold company details > and a DB per company so their data will be stored there? > How would I make sure that for every action in all the apps of my > project that is writes to the correct db for that client? > > > Any suggestions or help to push me in the right direction is > appreciated. > Thanks. > Google for "django multi tenancy". Should get you some idea of where to go next. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: django request xml
On Fri, Jul 29, 2011 at 9:54 AM, Exiawrote: > hi, I'd like to send an xml to a django web server. > I've written a python program like this: > > req = urllib2.Request('http://127.0.0.1/abc/', strxml) > f = urllib2.urlopen(req) > > but I don't know how to deal with it in views.py of django in the > server... > what should I do in the following function: > def hello(request): > ??? > When you post data to Django, the raw data posted is available in request.raw_post_data https://docs.djangoproject.com/en/1.3/ref/request-response/#django.http.HttpRequest.raw_post_data Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
django request xml
hi, I'd like to send an xml to a django web server. I've written a python program like this: req = urllib2.Request('http://127.0.0.1/abc/', strxml) f = urllib2.urlopen(req) but I don't know how to deal with it in views.py of django in the server... what should I do in the following function: def hello(request): ??? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Implementing one app for multiple users with their own data.
Hi, I've a web app which works nicely on a per user or per company basis. However I've gotten to the point where I want to run multiple companies through the same app(not have to redeploy for each client). However each client needs their own data and shouldn't be able to see other clients data. A DB per client is probably best but I'm not sure how I go about implementing this. In theory I'd like each client to be able to: -All log in at the same url. -Each have their own DB and own admin user etc. -All be running through the same web app. Do I need something like a master DB which will hold company details and a DB per company so their data will be stored there? How would I make sure that for every action in all the apps of my project that is writes to the correct db for that client? Any suggestions or help to push me in the right direction is appreciated. Thanks. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: about django
On Fri, Jul 29, 2011 at 8:51 AM, Phang Muliantowrote: > welcome to the club. ... > start with the documentation like others said, then more deep buy a book for > reference, then create a pilot project... Please tell me about pilot project. What is it? > On Jul 29, 2011 10:08 AM, "Harjot Gill" wrote: >> Refer the following site.It will really help you.This site will help >> you to learn django from starting and this are some tutorials that >> will help you to learn django. >> >> www.djangoproject.com >> >> Best of luck ! -- Jaspreet -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Template syntex error
On Fri, Jul 29, 2011 at 2:52 PM, nicolas HERSOGwrote: > How did u solve it ? There was an error in urls.py file Following was missing in the file: (r'^accounts/', include('userprofile.urls')), -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: How do I change my user password on Django's bug tracker?
Thanks! On Thu, Jul 28, 2011 at 8:51 PM, Jacob Kaplan-Mosswrote: > On Tue, Jul 26, 2011 at 7:07 AM, cool-RR wrote: > > How do I change my user password on Django's bug tracker? > > https://www.djangoproject.com/accounts/password/change/ > > If you've forgotten your password, see > https://www.djangoproject.com/accounts/password/reset/. > > Jacob > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: USE_I18N vs. USE_L10N
On Fri, 2011-07-29 at 18:21 +1000, Mike Dewhirst wrote: > https://docs.djangoproject.com/en/dev/topics/i18n/internationalization/ > - Internationalization > > https://docs.djangoproject.com/en/dev/topics/i18n/localization/ - > Localization > > https://docs.djangoproject.com/en/dev/topics/i18n/deployment/ - > Deployment of translations > > https://docs.djangoproject.com/en/dev/howto/i18n/ - Using > internationalization in your own projects > > ... and maybe when I've got it working I'll do an noob's overview. remember that all these were one page originally (and perhaps easier to understand. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Template syntex error
How did u solve it ? On Fri, Jul 29, 2011 at 11:17 AM, jaspreet kaurwrote: > My problem is solved > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Template syntex error
My problem is solved -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Crop feature in django application
I want to add crop option in Django application i followed the link: http://code.activestate.com/pypm/django-image-cropper/ By following the steps given in the link, it doesnot give any effect on application Is there more steps to do for adding crop feature Thanks -- Jaspreet -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: USE_I18N vs. USE_L10N
On 29/07/2011 5:38pm, Masklinn wrote: On 2011-07-29, at 05:56 , kenneth gonsalves wrote: On Thu, 2011-07-28 at 09:37 -0700, Lucy Brennan wrote: Before I comment, I would like to actually know if I got it right. In Django: USE_I18N: translation USE_L10N: localized formatting Right? wrong That's not what the Django documentation says, at least in my reading of it. I've been reading it since this thread began because I want to understand it. I'm finding it quite hard going but I think I'm getting somewhere. Here are the bookmarks I have on the topic so far ... https://docs.djangoproject.com/en/dev/topics/i18n/ - Internationalization and localization https://docs.djangoproject.com/en/dev/topics/i18n/internationalization/ - Internationalization https://docs.djangoproject.com/en/dev/topics/i18n/localization/ - Localization https://docs.djangoproject.com/en/dev/topics/i18n/deployment/ - Deployment of translations https://docs.djangoproject.com/en/dev/howto/i18n/ - Using internationalization in your own projects ... and maybe when I've got it working I'll do an noob's overview. hth Mike -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: USE_I18N vs. USE_L10N
On Fri, Jul 29, 2011 at 3:48 PM, Masklinnwrote: > On 2011-07-29, at 06:58 , Russell Keith-Magee wrote: >> To the rest of this thread: I want to head something off at the pass >> right now -- consider it a core-team decision that we're not going to >> rename these settings. I18n and L10n are well understood terms to >> anyone who has been dealing with adapting software to multiple >> languages and cultures reasonable descriptions of what Django does >> with the USE_I18N and USE_L10N settings, and we're not going to change >> the values because someone comes up with a slightly better name. There >> needs to be something fundamentally wrong or misleading before we >> would even consider changing the name of a setting, and given that >> these settings have been in the wild successfully for some time (I >> think it's 4 years in the case of USE_I18N) you're not going to find >> that here. > I think the issue with USE_I18N is not so much that it's been kept, but > that it was not expanded to cover USE_L10N's scope as well, with the > ability to enable or disable each subsection of the domain > (translations and localisation of value formats) added on top of that. > > I would have made more sense, to me, if USE_I18N enabled *all* of the > relevant l10n, m17n and i18n machinery and if new processes in this > field were added to the flag's purview as they were introduced, bringing > a django project with USE_I18N enabled ever closer to full "effective" > internationalization. If you think things could work better -- we accept patches :-) However, before you embark on a massive rewrite of Django's i18n and l10n systems, keep in mind that there are entirely valid historical reasons why the settings act the way they do -- mostly to do with maintaining backwards compatibility and retaining the ability to opt into potentially expensive (and confusing) options. Any proposal to change Django in a way that loses either of those properties won't be looked upon favorably. In particular, if you think the capabilities of USE_L10N could be subsumed by an expanded interpretation of USE_I18N, I think you need to take a much closer look at Django's source code, and the mailing list discussions that led to the introduction of the USE_L10N setting. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: USE_I18N vs. USE_L10N
On Fri, 2011-07-29 at 09:38 +0200, Masklinn wrote: > > wrong > That's not what the Django documentation says, at least in my reading > of it. i18n - preparing an app to be customised in *any* locale l10n - actually customising it for a *particular locale One can do i18n *without* doing *any* translation. i18n - marking strings for translation, l10n - translating the marked strings. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: USE_I18N vs. USE_L10N
On 2011-07-29, at 06:58 , Russell Keith-Magee wrote: > Lucy: Although there are a lot of people that use L10N and I18N > interchangeably, they are very distinct terms; any source you find > that uses them interchangeably is categorically wrong. However, the > two are very closely related, because localization usually happens in > the presence of internationalization, and vice versa -- hence the > common confusion. Although they share a Wikipedia page, if you read > the rest of the page, you'll see they make a distinction between a > localized system and an internationalized system. But as far as I read her messages, Lucy was not asking what L10N and I18N are, she was asking what USE_I18N and USE_l10N do. In Django. > To the rest of this thread: I want to head something off at the pass > right now -- consider it a core-team decision that we're not going to > rename these settings. I18n and L10n are well understood terms to > anyone who has been dealing with adapting software to multiple > languages and cultures reasonable descriptions of what Django does > with the USE_I18N and USE_L10N settings, and we're not going to change > the values because someone comes up with a slightly better name. There > needs to be something fundamentally wrong or misleading before we > would even consider changing the name of a setting, and given that > these settings have been in the wild successfully for some time (I > think it's 4 years in the case of USE_I18N) you're not going to find > that here. I think the issue with USE_I18N is not so much that it's been kept, but that it was not expanded to cover USE_L10N's scope as well, with the ability to enable or disable each subsection of the domain (translations and localisation of value formats) added on top of that. I would have made more sense, to me, if USE_I18N enabled *all* of the relevant l10n, m17n and i18n machinery and if new processes in this field were added to the flag's purview as they were introduced, bringing a django project with USE_I18N enabled ever closer to full "effective" internationalization. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: USE_I18N vs. USE_L10N
On 2011-07-29, at 05:56 , kenneth gonsalves wrote: > On Thu, 2011-07-28 at 09:37 -0700, Lucy Brennan wrote: >> Before I comment, I would like to actually know if I got it right. In >> Django: >> >> USE_I18N: translation >> USE_L10N: localized formatting >> >> Right? > > wrong That's not what the Django documentation says, at least in my reading of it. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.