Re: [MOVED] Renaming of mailing lists to avoid user confusion
On Tue, Aug 19, 2008 at 11:16 AM, Tom Tobin <[EMAIL PROTECTED]> wrote: > As an aside (and perhaps this is a topic for another thread), I really > don't like that "meta" discussion gets shoved off into -users; > django-users is *far* too high-traffic, and I don't keep myself > subscribed to it because I can't possibly keep up with 100+ messages a > day. Renaming issues aside — am I the only one who is bothered by how many messages-per-day -users gets vs. noticing "interesting" topics (where "interesting" depends on the individual, of course)? django-users has become such a catchall that I feel simply overwhelmed, and as I stated, I tend to simply not read it as a result. In the spirit of "bring me problems, not solutions" (with apologies to Jeff Croft), I've got a problem here; does anyone have a solution? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: [MOVED] Renaming of mailing lists to avoid user confusion
On Tue, Aug 19, 2008 at 11:16 AM, Tom Tobin <[EMAIL PROTECTED]> wrote: > Let me propose a stopgap: edit the django-users and django-developers > pages to state, in large bold text, what the purpose of each list is > (this is "edit welcome message" in Google Groups). Let's see if that > helps any, and come back to this in a month or so. Amidst the concern over split archives, filters, and topics (some of which is valid, I'll grant), I was disappointed to see this suggestion go unremarked. This is an *easy* action that might have immediate beneficial consequences, has no drawbacks, and will take someone all of five minutes to accomplish. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
[MOVED] Renaming of mailing lists to avoid user confusion
On Tue, Aug 19, 2008 at 8:16 AM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Please take this thread to django-users. This list is for the internal > development of django and this thread doesn't contribute to that. Done. On Tue, Aug 19, 2008 at 8:14 AM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > Seriously - this comes up every couple of months, and it's just a > bikeshed argument. We get about one off-topic post every ten days or > so; hardly an onerous task to gently point folks to the right place. > There's pretty clear explanations about what each list is for right > there on the sign-up pages; we'll just trade folks who ignore that > text for folks who ignore another bit. Those figures are off. We get roughly one off-topic post in django-dev every other day (considering August thus far, and not counting posters who immediately realized their mistake without prompting). And this *isn't* a bikeshed argument. There is obviously substantial confusion over what the terms "users" and "developers" mean in the context of Django. We're attracting *lots* of people (3849 on -developers, 10431 on -users), and the problem hasn't abated; it's only going to get worse. Let me propose a stopgap: edit the django-users and django-developers pages to state, in large bold text, what the purpose of each list is (this is "edit welcome message" in Google Groups). Let's see if that helps any, and come back to this in a month or so. On Tue, Aug 19, 2008 at 8:16 AM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > What will happen is that this thread will generate far more > traffic than the infrequent accidental mis-postings and clog up the > recent postings in our inboxes, obscuring stuff that gets actual > development work done. As an aside (and perhaps this is a topic for another thread), I really don't like that "meta" discussion gets shoved off into -users; django-users is *far* too high-traffic, and I don't keep myself subscribed to it because I can't possibly keep up with 100+ messages a day. It's high about time that -users got split into a couple of different lists (IMHO "django-support", and "django-community"). I'm completely fine with the development list staying completely on the topic of, well, *development*, but the way "django-users" has become "django-catchall" is fairly detrimental to focusing on what's of interest to various individuals. (FWIW, I've registered "django-support" and "django-community" as locked groups, and will gladly hand them over to someone in core / DSF / etc.) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Chicago Djangonauts Meeting Tomorrow, May 29
Join us tomorrow for the first meeting of the Chicago Djangonauts! When: Thursday, May 29 @ 6:30p Where: Mercury Cafe, 1505 W Chicago Ave, Chicago IL Location info: http://www.chimercurycafe.com/ This first meeting will be informal -- just lounging and chatting. We're not expecting too many people, but feel free to come and surprise us! I'll probably be wearing a hat with cat-ears or a pig-face, so just look for the crazy guy. ;) Via CTA, you can take bus route #66 west-bound from the Chicago Blue or Brown stations to Chicago and Greenview; Mercury is right across the street to the southwest. (Google Transit and Street View rock.) The Chicago Djangonauts have a mailing list for the interested: http://groups.google.com/group/django-chicago --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Chicago Djangonauts list / meetings
I've started a Chicago Djangonauts list; apologies for the noise for the 99%+ of you not in the Chicago area. :-) http://groups.google.com/group/django-chicago I'll be starting discussion soon about when and where our first meeting should be (sometime in May); if we have enough interest, we'll make it a monthly thing (probably during those weeks ChiPy isn't running). --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Are you getting caught in the Django Trac's spam filter? Read this.
It seems I've been designated the "Django spam maven"; what this means for you, if you've been getting caught in the Django Trac's spam filters, is that you need to write me and let me know your IP address (or the typical range of IP addresses you use) so I can whitelist you. Once I do this, you won't trigger the "Akismet rejected spam" or any other spam-rejection errors. Tom Tobin [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: MR: _manipulator_validate_FIELD() methods?
On 8/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Tom, > > Does the solution I posted [1] earlier in this thread not work for you? > > > [1] http://groups.google.com/group/django-users/msg/a76be4c94631ec80 Getting these manipulator-aware validators working in the admin is exactly the issue I want to solve; I came up with a proposal to reinstate similar behavior to pre-MR-removal Django and posted it to Django-dev. I now have both mentioned potential solutions working; it's just a matter of deciding which one I prefer (or, quite likely, having someone else smarter than me hit me with a stick and point out a superior way of doing 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: MR: _manipulator_validate_FIELD() methods?
On 5/6/06, Matthew Flanagan <[EMAIL PROTECTED]> wrote: > > On 5/6/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > > > Matthew Flanagan wrote: > > > > >Since MR merged the _manipulator_validate_FIELD() methods stopped > > >working. The solution I came up with was to write custom manipulators > > >(which was what I was trying to avoid all along). > > > > > Can you assign those validators to the validator_list of a field right > > in a model? I never had a chance to use _manipulator_validate_FIELD() so > > I don't know if there is any difference. > > > > The validator functions assigned to a models validator_list only take > two arguments eg. isValidField(field_data, all_data). Where as they > _manipulator* ones looked like this _manipulator_validate_FIELD(self, > field_data, all_data), where 'self' was the manipulator instance. The > latter were automatically added to the model's manipulator in > pre-magic-removal. I know this is an old thread, but I just ran into the same issue on trunk: I have no idea how to duplicate the _manipulator_validate_FIELD behavior from pre-MR in order to access fields from the original object in a validator. I can't find anything in the current docs or in the source which might indicate how to do this; anyone have any pointers? :-) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: psycopg2
On 7/30/06, Vance Dubberly <[EMAIL PROTECTED]> wrote: > postgresql_psycopg2 > > Yes I found it. Yes I know it's not supported . But could somebody tell me > how to tell it to shut up? My eyes are bleeding! :) The debug output is > just a little overwhelming and quite useless unless you are the module > developer. Is there switch somewhere I could flip without shutting off > debugging for everything? See the last question here: http://initd.org/tracker/psycopg/wiki/PsycopgTwoFaq In short, rebuild psycopg2 after yanking PSYCOPG_DEBUG from "define" in setup.cfg. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Sniffing around django
On 6/27/06, Tom Tobin <[EMAIL PROTECTED]> wrote: > On 6/27/06, toth anna <[EMAIL PROTECTED]> wrote: > > > > Tom Tobin <[EMAIL PROTECTED]>: > > > You should be able to get the behavior you want by > > overriding the > > > save() method on your models. > > > > Is there any usable examples somewhere for me? > > Here's the general idea: > > http://www.djangoproject.com/documentation/models/save_delete_hooks/ > > In the save() method, place whatever logic you want to run before you > call the "real" save() via super(). Argh. I *really* have to keep better track of which list I'm posting/replying to; this thread belongs on django-users. :-) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Sniffing around django
On 6/27/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > On Jun 27, 2006, at 9:58 AM, toth anna wrote: > > I'm working on my thesis in our academy (i have to > > implement, too). > > Searching for an enviroment, i found django, and it looks > > very nice. > > After reading tutorial, i have some questions (and more to > > come...:) before i fall in love with it. > > > > Is there any (elegant) opportunity for a "container level > > logic". For example, there can be only 5 from a specific > > type of item, and inserting a new, we have to delete oldest > > object. > > Or when saving an object, container "splits" it, and creates > > two instead (from my example, if "date period" object > > contains a year boundary, i have to split it), without > > affecting "caller". > > > > Thanks for your help, > > > > Anna > > This question is best asked on django-users; I'm redirecting this > thread there. > > Jacob Oops, that's what I get for having Gmail dump both django-dev and django-users into the same label. :p My reply on django-dev was a one-liner: "You should be able to get the behavior you want by overriding the save() method on your models." --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: MS SQL Django suport is stable?
On 6/21/06, mamcxyz <[EMAIL PROTECTED]> wrote: > > I'm triying to setup a linux box with django, and frankly, I never > spect this task can be so HARD. Every step is a nightmare, I need > compile everything, the YUM/APT only have out-dated versions of the > things I need to run django. I have the feeling you won't care at this point, but not all Linux distributions are created equal; some lag far behind recent software updates, while others are much closer to the cutting edge. Ubuntu Linux, in particular, makes it ridiculously fast and easy to get up-to-speed with a working Django installation; you shouldn't have to compile *anything*. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Django Quick Start with Schema Evolution Support
On 6/4/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote: > > I've create a simple Schema Evolution Support for Django and I am > working to created a Django Quickstart, which will allow even > unexperienced users to see a django site running within their browsers. Ilias Lazaridis is a known mailing list and Usenet troll, and is therefore being ignored by this community. Any statements by Ilias Lazaridis should be considered incorrect, inaccurate, or otherwise tainted with the intention of disrupting conversation on django-users and/or django-developers. Reference: - http://en.wikipedia.org/wiki/Internet_troll - http://en.wikipedia.org/wiki/Ilias_Lazaridis - http://www.encyclopediadramatica.com/index.php/Ilias - http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/138966 --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: slug as primary key: any reason why not?
On 5/9/06, gabor <[EMAIL PROTECTED]> wrote: > > are there any scenarios when it's not a good idea to have [Slugs] as > primary keys? (except some hypothetical situations) The short answer: it's always a *bad* idea. The slightly longer answer: It's generally a bad idea to have your primary key be a field with any sort of external meaning; that's why an arbitrary, autoincremented serial/integer field is typically used. If you use a slug (for example), your data integrity is hosed the moment your slug changes (perhaps because you changed the title); all foreign references to that object will become invalid. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: check for none
On 4/12/06, Jiri Barton <[EMAIL PROTECTED]> wrote:
>
> how do I check if a variable is None in a template?
>
> I want to be able to discern among None, empty list, and non-empty
> list; then, I want to tell the user - say nothing, "nothing found",
> "found the following:" resp.
This is likely a sign that you're trying to cram too much "programmer"
logic into the template. :-) Pass in a search_was_performed variable
or whatnot into the template's context:
{% if search_was_performed %}
{% if search_results %}
{% for item in search_results %}
... do stuff ...
{% endfor %}
{% else %}
"No search results were found."
{% endif %}
{% endif %}
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: Django svn over https?
On 4/10/06, Adam <[EMAIL PROTECTED]> wrote: > > Augh, ok, sort of nevermind. Right after I hit "post", the guy who told > me our firewall wouldn't support WebDAV over http told me we have an > http proxy outside the firewall that I could use. So problem solved for > me, but it still might be useful for others with similarly draconian > firewall issues. This is an issue that should be taken up with one's system administrator(s); if you need to access a resource to do your job, yet your organization will not allow you the means to do so (even after requesting such, and especially when those means do not exactly fall into the realm of the exotic, e.g., accessing a public subversion repository over HTTP), you might want to question the sanity of your organization's policy-makers, and act accordingly. :-) Changing Django's repository to allow HTTPS access would be addressing the symptom here, not the disease; what's even worse is that enough of such concessions might convince daft system administrators that they need to clamp down on the *workarounds* (e.g., HTTPS), rather than addressing the draconian policy itself. Hopefully many such policies are less harsh than they first appear, allowing use of approved methods (e.g., proxies) when the need arises for developers. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Advice on developing with django for a team of 10+
On 3/16/06, tonemcd <[EMAIL PROTECTED]> wrote: > > 3. People run their own local django installations, and commit changes > to a development server for testing before those changes are sent to > the deployment server. This means each individual user machine has to > have access to the databases and keeps a copy of the source on their > machine. It also means a lot of django trunk duplication on each > machine (I guess we could do an 'svn up' where the target is our own > django installation on the server - nice thought!). We have very little > experience of using svn etc however. I couldn't imagine managing 10 developers on a project without a revision control system. Subversion is easy to learn and easy to use; I'd highly recommend you go that route with your project. Good luck -- and I'm glad to see you picked Django! :-) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Django in Boo
On 3/5/06, gabor <[EMAIL PROTECTED]> wrote:
>
> >>> def f(y):
> ... x = y * 3
> ... return x + y
> ...
> >>> f(5)
> 20
> >>> f('_django_')
> '_django__django__django__django_'
> >>>
>
> you know...this whole 'static typing' thing is a little a double-edged
> sword, isn't it? :))
You know, my first thought there was "badger badger badger badger" . . . :-p
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: Django in Boo
On 3/3/06, wizeman <[EMAIL PROTECTED]> wrote: > > Hi. I'm just starting to use Django and I'm loving it. > > Don't you think it would be great if Django was ported to Boo ( > http://boo.codehaus.org/ ) ? Err, knock yourself out porting it if you want (as it's BSD licensed after all), but I don't think you'll see many of us jumping to switch from Python anytime soon. ;-) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: postgresql
On 2/26/06, Mary Adel <[EMAIL PROTECTED]> wrote: > > I am using Django and now and i published my website but the problem is > that admin is not that good and sometimes he damages somethings so i > need to take a backup from the database of my project every night but i > don't know how to do this if anyone can help me > I am using postgresql You're asking a PostgreSQL (or MySQL, or sqlite, etc.) question, not a Django question; check out the website for whatever database you're using and see if the documentation explains how to handle backups (it *should*, I'd hope!). --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Magic-removal roadmap?
On 2/25/06, Nicholas Matsakis <[EMAIL PROTECTED]> wrote: > > > Is there a (rough) timeframe set out for when the magic-removal branch > will be merged into the trunk? Will there be a Django release before that > which will incorporate all the improvements aside from the magic removal? > I'm not looking for exact dates, just where these events are likely to > happen in three months, six months, or longer. I'd guess that m-r will be merged to trunk before the end of March; there's a feeling that it's been branched for too long, and it's time to wrap things up. The Django sprint at PyCon this upcoming week should hopefully make serious inroads here. The next release should follow on the heels of the merge back; if you want the non-m-r features today, trunk is the place to be. :-) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: How To Calling a Flat page
On 2/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I am a bit unclear as to how to call a Flat page. > > I 've done the necessary work, created the default template, got > flatpages showing up in the admin and followed the instructions. Eg. my > Introduction page is named /int/. Did you add the middleware that goes along with it? :-) > In my template I just try to reference it as href="/int/" but this does > not work. > > I understand to usual url-view-template senario, but I am a bit lost > here. The docs do not seem to suggest that you need to write a URL > rule. You're right, you don't; what happens when you have the flatpage middleware installed is that when you trigger a "page not found" error, it goes and checks the flatpage table to see if there's a flatpage for that location, and if so, returns it instead of the 404 error. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: flatpages
On 2/22/06, Mary Adel <[EMAIL PROTECTED]> wrote: > > how to call in flatpage a content i have saved in the database > ex i saved the path of the css and java script in the database and i > need to call it in my flatpage so how i could do this If those files change on a flatpage-by-flatpage basis, you might be better off making your own version of Flatpages with fields for the CSS/JS locations; you could then pass those into the template as appropriate. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Css and Javascript
On 2/22/06, Mary Adel <[EMAIL PROTECTED]> wrote: > > I need to save the Css and the Java script file in the database so as i > can make the user change it easily so how i can do this in an easy way You could clone Flatpages for the other file types and ForeignKey each flatpage to a CSS entry and a Javascript entry; make sure you consider the potential performance issues if you go that route, though. (There's a reason people tend to serve CSS and Javascript from static media servers even if the site itself is dynamic.) :-) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: adding page
On 2/20/06, Mary Adel <[EMAIL PROTECTED]> wrote: > > I have a question and i have deadline tomm :( and really i need help > I build a model called pages which has page name and page link and page > content and then i build the database and i make the admin interface to > fill all the data but the problem is that: > I need to add page dynamically without adding by hands in the url.py > file any lines and then add a function in the view.py file For a start, have you taken a look at the flatpages module? Your need sounds fairly close to what flatpages does, as far as I can tell. http://www.djangoproject.com/documentation/flatpages/ --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: urllib2.open failing in Django?
On 2/20/06, Ned Batchelder <[EMAIL PROTECTED]> wrote: > > I found the problem on my end. It was a call to > socket.setdefaulttimeout(). The bug I had found but can't locate now > was correct: if you call that socket function, urllib2 (and httplib) > have very difficult times completing reads. Was the value you passed in through setdefaulttimeout() particularly small, by any chance? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Django+Postgre+Apache+Windows
Okay, smack me for reading the subject line one second after hitting Send. :-p On 2/12/06, Tom Tobin <[EMAIL PROTECTED]> wrote: > On 2/11/06, David S. <[EMAIL PROTECTED]> wrote: > > > > Sorry for the lack of details, but any guidance is appreciated. > > That's where I'd start — more details. ;-) Can you tell us, e.g., > what platforms the two machines are running? >
Re: Problem adding new classes to a model
On 12/30/05, aaloy <[EMAIL PROTECTED]> wrote: > OK. That should be the problem! > It would be nice to have an option to generate these inserts also.. There is. :-) django-admin.py sqlall model_module_goes_here or just django-admin.py sqlinitialdata model_module_goes_here If you don't need everything it spits out, just cherry-pick the relevant lines out for your model/table.
Re: Search Functionality
On 12/29/05, David Pratt <[EMAIL PROTECTED]> wrote: > > Doesn't Swish-e pose an incompatibility for licensing? Everything Django > has been BSD up to this point and I would hate to see anything alter > this. Isn't swish-e gpl? Swish-e grants a special exemption from automatically GPL'ing linked programs which use the libswish-e API interface: http://swish-e.org/license.html
Re: TimeField Problem/Question
On 12/8/05, Daniel Ericsson <[EMAIL PROTECTED]> wrote: > There seem to be a fix in the new-admin branch -> http:// > code.djangoproject.com/changeset/1244 Or, in other words, the current trunk, since new-admin got merged a little while back. :-) In general, if you're having a problem and you're using 0.90, try out trunk to see if your problem has already been solved -- just like magic! :-D
Re: customizing admin
On 11/29/05, Medium <[EMAIL PROTECTED]> wrote:
>
> Robert Wittams wrote:
>
> >Medium wrote:
> >
> >>4. Can we change the template {{ variable }} to something like
> >>${variable} I don't mind the {% %} but {%starttag%}{{var}}{%endtag%}..
> >
> >You can assume this is not going to change, it would break too much for
> >very little benefit. I guess you could monkey patch
> >django.core.template.VARIABLE_TAG_START and
> >django.core.template.VARIABLE_TAG_END if you wanted to. It would be kind
> >of silly though.
> >
> You're right about the little benefit, but this syntax ${var} or $var is
> very widely used in many template solutions across all languages and
> provides a level of familiarity to most template users. Easier migration
> and therefore wider adoption may prove a benefit which isn't as obvious now.
I'm sorry, but I can't help but think that a user who is skilled
enough to be comfortable with a alternate but not-wildly-different
syntax, yet who would face major difficulties adjusting to Django's
syntax, has other problems than the syntax at hand. :-) FWIW, I
actually find Django's template syntax easier to read and use than
dollar-sign based syntax (which in turn feels alien and Perl-ish to
me).
Re: problem marketing django to php folk
On 11/26/05, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > > hi, > have been talking to some php folk about switching to django, but > they have raised a serious concern: Django website does not have a > page for security alerts and the django team has not released any > security patches - so they feel very uneasy about the whole thing. > Can this defect somehow be rectified? Err... 1.0 isn't even out yet. :-D
Django Trac Spam
Someone's been spamming the Django Trac today, screwing up tickets and whatnot. Is there any way to fix and/or prevent this?
Re: Paginating complex queries
On 11/22/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> What is the Django Way (tm) to paginate complex queries with
> user-controlled parameters? That is, if I want to paginate the results
> of a foos.get_list({'lots': 'of_complex', ['junk': 'in here']}) where
> the query terms are submitted via form, how should I go about that
> while maintaining the user-posted values from page to page?
This looks like a case where generic views, combined with the code
from ticket #667 (specifically, the second patch), might come in
handy:
http://code.djangoproject.com/ticket/667
I wrote the current patch implementation, so I'd love to hear any
suggestions or criticism. :-)
Re: ZODB Anyone ?
On 11/20/05, bruno modulix <[EMAIL PROTECTED]> wrote: > Only data are saved to the zodb. But you're still working with it solely in the form of a Python object (with aforementioned methods and all). With a SQL DB, you can access that data in a variety of ways, move it to a different database implementation, and you're not tied specifically to Python and the ZODB. > > I also find changing a > > model under an object database to be messier than changing one with a > > relational database. > > This has nothing to do with MVC. As for the "mess", it depend on what > you are changing and how your object graph is structured. I'm sorry if it seemed I was implying it was directly related to MVC; it was more of an "aside" with regards to another perceived disadvantage. > > Overall, I prefer the clearly delineated > > separation a relational database provides between my data and what I'm > > using it for. > > > > And ? Is that all you have to support your previous assertions ? "C'est > un peu court, jeune homme". No, it's merely a conclusion. (And I fear I'm ignorant of languages other than English. :-) )
Re: Patch to get the timezone right in the settings.py on linux
On 11/20/05, Brett Parker <[EMAIL PROTECTED]> wrote: > Attached is a patch against current svn (applies to 0.90 also), that > automatically sets TIME_ZONE and LANGUAGE_CODE according to the hosting > system. The best place for patches is Django's Trac: http://code.djangoproject.com/
Re: ZODB Anyone ?
On 11/20/05, Cheng Zhang <[EMAIL PROTECTED]> wrote: > > I am curious to learn more about why "object DBs are not good fit for > the MVC-like separation". Previously I had very basic exposure to > ZODB, along with the concept of object database, when I played with > Zope a bit years ago. Because with ZODB, for instance, actual Python code objects are living in your database -- code objects that likely have methods attached to them for manipulating their own data, etc. I also find changing a model under an object database to be messier than changing one with a relational database. Overall, I prefer the clearly delineated separation a relational database provides between my data and what I'm using it for.
Re: ZODB Anyone ?
On 11/19/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > This has never been tried, to my knowledge. It would be possible -- > and relatively easy -- to do if there were a DB-API-compliant ZODB > library. Is there one? I know nothing about ZODB, other than the fact > that it's associated with Zope. I think. ZODB is an object database, not a relational one; based on my experience with it and other object DBs, it's not a good fit for the MVC-like separation Django adheres to.
Re: Creating new tables
On 11/15/05, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > > Not true; you can set up a model to deal with a database created by > > hand (although I'm not sure why you'd want to *purposely* create a > > database for Django by hand; it does a good job of taking care of > > that for you). > > what i meant was that unless you have a model, you cannot access the > table through django - it is irrelevant whether the model came first or > the table came first. Ahh, then panos is asking for strange behavior. :-)
Re: Creating new tables
On 11/14/05, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > > On Tuesday 15 Nov 2005 12:26 am, panos wrote: > > b. can the new tables be accessed using the database API? > > no Not true; you can set up a model to deal with a database created by hand (although I'm not sure why you'd want to *purposely* create a database for Django by hand; it does a good job of taking care of that for you). Now, if you want to *change* your model later on -- that's where you're forced to do things manually.
Repeating Blocks Within a Template
A bit stumped here . . . Is there a recommended convention for repeating blocks within a template? e.g., I have a paginated object_list generic view, and I want to repeat my pager code (i.e., "back", "next") at both the top and bottom of the list without copying and pasting. -- Tom
