Re: #1443: strftime for date and datetime before 1900

Is there any movement on this issue? I'm working on designing a site dealing with historical data and pretty much all of the dates involved are before 1900 (1600-1800). Would be really nice to get a solid solution on this. On Mar 19, 10:45 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On

Re: Unfair ticket management

I'm not a fan of this discussion, I understand what you're saying, and the simple importerror test should suffice, otherwise its going to get to a point where we're going to have to keep a list of python libraries that can't be used for app names. Its not going to work like that. As far as I'm con

Re: Unfair ticket management

On Mar 31, 9:08 pm, Ivan Illarionov <[EMAIL PROTECTED]> wrote: > On Mar 31, 7:36 pm, Thejaswi Puthraya <[EMAIL PROTECTED]> > wrote:> First, I am very sorry to have caused so much of pain to you. I > > totally overlooked your ticket (just missed it) in an urge to > > contribute during the sprint. W

AutoCad Software Free Download & AutoCAD 2009 is coming

*ttp://www.designhelp4you.blogspot.com/* *http://www.designhelp4you.blogspot.com/* *http://www.designhelp4you.blogspot.com/* * * *Auto CAD EBOOKS*

Re: Refactoring the documentation

On Mon, Mar 31, 2008 at 7:25 PM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > Technology helps in some places, but there's no replacement > for a good editor. And I'm *not* talking about Emacs. The next release will have 'M-x copyeditor' for that, actually... -- "Bureaucrat Conrad, you are

Re: Refactoring the documentation

On Mar 31, 8:25 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > On Mon, Mar 31, 2008 at 6:25 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >  I'm wondering if something likehttp://django.reddit.com/shouldn't > >  get some sort of official blessing for listing/searching those blog > >  po

Re: Refactoring the documentation

On Mon, Mar 31, 2008 at 6:25 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I'm wondering if something like http://django.reddit.com/ shouldn't > get some sort of official blessing for listing/searching those blog > posts which aren't of good enough quality for inclusion in the > official

Re: Refactoring the documentation

On Mon, Mar 31, 2008 at 4:36 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > One thing I'm trying to figure out in my small set of docs is how > frequently I want/plan to use the index and glossary functionality > that comes with sphinx. How much additional meta data do you hope to > add to

Re: Refactoring the documentation

This all sounds really awesome! >     * Cross-sectional how-tos: we've only got a few of these currently. This >       is the area where bloggers are doing a wonderful job these days. The >       problem with this blog material is that it usually doesn't every get >       updated, so it eventuall

Re: Refactoring the documentation

I won't bother responding to anybody in particular, because I'm in agreement with so many on this thread so far. I'm glad to see this refactoring happen, because a doc improvement can only make things better for everybody. I know you're not getting into details yet, but once you do get down to it

Re: Refactoring the documentation

On Mon, 2008-03-31 at 13:45 -0500, Jacob Kaplan-Moss wrote: [...] > * Internals: not so hot; in fact, we've really only got the contributing > document. Help is needed here. There's http://code.djangoproject.com/wiki/DevModelCreation. It needs to be updated when model inheritance lands

we need something like this in Django json encoder

This following code was very helpful, something like this in Django would be greatly appreciated, I wish I had seen it earlier, would have saved me 2 days of effort. http://blog.michaeltrier.com/2007/7/30/json-generic-serializer --~--~-~--~~~---~--~~ You received

Re: Refactoring the documentation

I've been looking at using the sphinx tools for overhauling the Satchmo documentation too. There's far far less documentation in that project so it is easier but I am anxious to see how you do it. IMHO, Django really has some best practices with documentation so I appreciate the fact that you're k

Re: Refactoring the documentation

On Mon, Mar 31, 2008 at 4:01 PM, J. Cliff Dyer <[EMAIL PROTECTED]> wrote: > Since all the documentation is already in subversion, it might make > sense to have a docs-refactor branch on the tree. I'd rather not -- I don't want to get sucked into thinking I have a long time for this. As long as

Re: Refactoring the documentation

On Mon, Mar 31, 2008 at 2:29 PM, Tim Chase <[EMAIL PROTECTED]> wrote: > Ah, the curse of backwards compatibility and permalinks. My one > concern (okay, given more time to think about it, perhaps more > will percolate to the surface) with this is the abundance of > (legacy) HTML-fragment refe

Re: Refactoring the documentation

On Mon, 2008-03-31 at 13:45 -0500, Jacob Kaplan-Moss wrote: > Right. How will I do this, you say? Here's my plan: > > * Using the outline from the existing documentation > (http://toys.jacobian.org/django/docoutline-r7392/), make a new outline > and figure out where each bit fits

Re: Refactoring the documentation

Tim Chase wrote: > Ah, the curse of backwards compatibility and permalinks. My one > concern (okay, given more time to think about it, perhaps more > will percolate to the surface) with this is the abundance of > (legacy) HTML-fragment references that reside in the ML archives, > such as >ht

Dynamic Subdomain generation for users

Hi guys. I'm developing a system that gives a user a sub domain for their account. I found this article, http://www.rossp.org/blog/2007/apr/28/using-subdomains-django/, which is really helping. But the problem I'm having trouble thinking through is how I could give sub domains certain urls that

Re: Dynamic Subdomain generation for users

I apologize, I did not see that I was posting this to Django Developers. My mistake. On Mar 31, 2:33 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi guys. > > I'm developing a system that gives a user a sub domain for their > account. > > I found this > article,http://www.rossp.org/blog

Re: Refactoring the documentation

> Am I missing anything here? > > So feedback is welcome, please give it. Ah, the curse of backwards compatibility and permalinks. My one concern (okay, given more time to think about it, perhaps more will percolate to the surface) with this is the abundance of (legacy) HTML-fragment references

Re: Refactoring the documentation

I like it, the problem becomes a bit more obvious if you look at something like the templates for developers page, which is pretty messy and contains a lot of different topics, or something like the newoforms docs, which are just huge and could probably do to be broken down a lot. And of course,

Re: GSoC proposition - djangosearch backend

Yes, but in djangosearch you will have support for many search engines with very simple API. On 31 Mar, 20:16, Alex Koshelev <[EMAIL PROTECTED]> wrote: > Do you see: > -http://code.djangoproject.com/wiki/TextIndexingAbstractionLayer > -http://code.google.com/p/djapian/ > -http://code.google.com/p

Refactoring the documentation

I'm embarking on a mission to refactor Django's documentation; this is where you give me feedback about how much crack I'm smoking. Keep in mind that most of this post fits into the "heads-up" category: if I'm not asking for feedback on some point it's because I've made up my mind. Only argue with

Re: GSoC proposition - djangosearch backend

Do you see: - http://code.djangoproject.com/wiki/TextIndexingAbstractionLayer - http://code.google.com/p/djapian/ - http://code.google.com/p/django-sphinx/ ? On Mar 31, 8:39 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi, > > My name is Grzegorz Swierad and I am interested in participati

Re: GSoC proposition - djangosearch backend

Yes, You right. This is not big enough. I can try to create more backends, but I don't know how many I make it. Grzegorz On 31 Mar, 18:49, "Joseph Kocherhans" <[EMAIL PROTECTED]> wrote: > On Mon, Mar 31, 2008 at 11:39 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Hi, > > > My name is

Re: Customizable QuerySets

On Mon, Mar 31, 2008 at 5:27 AM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > If you want to be able to specify a different default manager for some > particular use of an existing model, you're sort of after a third type > of model subclassing that I've thought about but haven't implemented

Re: GSoC proposition - djangosearch backend

On Mon, Mar 31, 2008 at 11:39 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > My name is Grzegorz Swierad and I am interested in participating in > Google Summer of Code for Django. I study in University of Zielona > Gora in Poland. I have more than one year experience with Django

Re: Customizable QuerySets

> If you want to be able to specify a different default manager for some > particular use of an existing model, you're sort of after a third type > of model subclassing that I've thought about but haven't implemented: > subclassing an existing model and explicitly telling Django that this is > onl

GSoC proposition - djangosearch backend

Hi, My name is Grzegorz Swierad and I am interested in participating in Google Summer of Code for Django. I study in University of Zielona Gora in Poland. I have more than one year experience with Django. I create sites: http://mines20.com or http://plom.pl . I wish to create a Xapian backend fo

Duplicate tickets

Just changed the subject. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email t

Re: Unfair ticket management

On Mar 31, 7:36 pm, Thejaswi Puthraya <[EMAIL PROTECTED]> wrote: > First, I am very sorry to have caused so much of pain to you. I > totally overlooked your ticket (just missed it) in an urge to > contribute during the sprint. Will be careful from the next time. The > patch for ticket #6789 too wa

Re: Unfair ticket management

On Mar 31, 5:19 pm, Ivan Illarionov <[EMAIL PROTECTED]> wrote: > > There are people doing triage regularly to check for duplicates; > > however, there are a large number of tickets and this one -- as > > mentioned above -- happened during the development sprint when there > > was already a large a

Re: Unfair ticket management

> There are people doing triage regularly to check for duplicates; > however, there are a large number of tickets and this one -- as > mentioned above -- happened during the development sprint when there > was already a large amount of ticket activity. Try not to take it > personally or allege unf

Re: Unfair ticket management

On Mon, Mar 31, 2008 at 6:52 AM, Ivan Illarionov <[EMAIL PROTECTED]> wrote: > Hey, I've just found that ticket #6789 was merged into trunk while my > ticket #6654 that was filed a month earlier and does the same thing > was ignored. The one that was checked in appears to have had its patch att

Re: Django admin Error at /admin/auth/user/1/?

Just to explain my motivation: it wasn't so much to optimize the core devs' time, though that is a concern, but to make on-ramping new users as friction-free as possible. If there's a common error that newbies make, we can either provide an error message ("wrong group"), or try to fix the syst

Re: Unfair ticket management

Ivan, I'm sure the developers do check for duplicate tickets, but they're busy people. Not to mention with nearly a thousand tickets open, it can be difficult to remember all of them and easy to miss one. I might suggest coming here with an air of curiosity instead of an accusatory tone for best r

Re: Django admin Error at /admin/auth/user/1/?

On Mon, 2008-03-31 at 07:11 -0400, Ned Batchelder wrote: > I figured the name of the group is hard to ignore. By making the name > more specific, people would be more likely to find the appropriate > group. Yeah... I know where you're coming from. It's hard to tell if the change will work or no

Unfair ticket management

Hey, I've just found that ticket #6789 was merged into trunk while my ticket #6654 that was filed a month earlier and does the same thing was ignored. My patch is still better because it removes INVALID_PROJECT_NAMES that became unnecessary -- all those names will be detected by __import__. Why

Re: Django admin Error at /admin/auth/user/1/?

I figured the name of the group is hard to ignore. By making the name more specific, people would be more likely to find the appropriate group. --Ned. Malcolm Tredinnick wrote: > On Sun, 2008-03-30 at 22:01 -0700, simonbun wrote: > >> Maybe it could be useful to add a description to this lis

Re: Django admin Error at /admin/auth/user/1/?

Indeed, but maybe the description could be added to the top of the list on http://groups.google.com/group/django-developers/topics or http://groups.google.com/group/django-developers to make it a bit harder to miss. But I agree, no solution would be 100% fool proof. Simon. On Mar 31, 7:50 am,

Re: Customizable QuerySets

On Sun, 2008-03-30 at 13:31 -0700, [EMAIL PROTECTED] wrote: > > Agreed. In fact, this exact suggestion was made during the recent > > discussions about adding aggregates. I'd much rather see per-manager > > customization of Query Sets, rather than a global setting. > > What do you think about my