On Sat, May 9, 2009 at 9:33 AM, Adys wrote:
>
> I've been working on DurationFields this evening (ticket #2443)[1]. My
Hi Jerome,
Most of the people that could give you the feedback you are requesting
are currently working hard to get version 1.1 out the door. If you
wait a couple of weeks for
Hi all
I've been working on DurationFields this evening (ticket #2443)[1]. My
implementation is working pretty well with a single TextInput. I'm
storing the durations as Decimal in the database (since from what I've
heard storing them as a 64-bit int is a no-go), in microseconds.
When creating or
Hello all,
It's been a busy week. I haven't gotten anything visible done. I've
got a lot of prep work and learning done (with my dev environment,
revision control, etc), but nothing spectacular. School ends next
week, so I am looking forward to getting moving on my interim ticket
once it does.
C
It's Friday, and that means it's time for a progress update on my GSOC
project, Admin UI Improvements.
I'm getting a hang of the patch submission process as well as better
understanding of the code around the admin interface. This week, I fixed my
second Django ticket ever #10992.
At this point, t
Hi Alex,
On Fri, May 8, 2009 at 16:04, Alex Gaynor wrote:
> Hello All,
>
> I've spent the past week at EuroDjangocon, and as such I've had the
> opportunity to discuss multi-db stuff with a bunch of very smart people.
> Simon and I resolved the issue of DSNs vs. dicts (as long as Simon can
> dyn
Hello All,
I've spent the past week at EuroDjangocon, and as such I've had the
opportunity to discuss multi-db stuff with a bunch of very smart people.
Simon and I resolved the issue of DSNs vs. dicts (as long as Simon can
dynamically add a new DB he's happy). Otherwise nothing has changed.
Pers
On Fri, May 8, 2009 at 6:25 AM, OverKrik wrote:
>
> Hello, I am working on heavy-AJAX-based website and use firebug alot
> to check responces from server, in case of 500 error Django sends full
> 500 page which is not very easy to use. I've made a simple patch to
> provide light version of 500 pa
On May 8, 2009, at 11:25, OverKrik wrote:
> Hello, I am working on heavy-AJAX-based website and use firebug alot
> to check responces from server, in case of 500 error Django sends full
> 500 page which is not very easy to use. I've made a simple patch to
> provide light version of 500 page in cas
Ok, So this update will be quick as I had a pretty uneventful week, as
opposed to most of the django community, which apparently had a crazy week
at EDC *Envy* GRR ;) . I worked on getting a ticket fixed:
http://code.djangoproject.com/ticket/8968
But not a whole lot else. I wrote a _lot_ of te
+1
I think Warren's suggestion is the clearest. I also like the "core
developers" bit, but I would put that in as a second sentence.
Something like:
"""
Discussion group for issues regarding the development of the Django
framework itself. This is primarily for core developers. For
discussion
> How about:
>
> "You're found the wrong list. You're probably looking for django-users
> unless you're interested in the development of the Django framework itself."
+1
[waves hand] This is not the list you are looking for.
-tim
--~--~-~--~~~---~--~~
You
On Fri, May 8, 2009 at 9:58 AM, Edwin Wong wrote
>
> Having followed the group here for some time, anybody posting a job
> posting or similar off-topic posting tends to be a first time poster,
> and in most cases it's very obvious that they never even bothered to
> read the group description. Th
Don´t make a core list, put inside the dajngo site
a new applet for register jobs, like have in the python.org[1]!!
Its simple and best for all! ;)
hugs,
Marcello Bontempo Salgueiro
[1] http://python.org/community/jobs/
- Original Message -
From: "Dave Smith"
To: django-develope
Big bold letters:
*** THIS LIST IS NOT FOR DJANGO HELP - USE DJANGO USERS FOR THAT ***
On Fri, May 8, 2009 at 10:26 AM, Dave Smith wrote:
> On Fri, May 8, 2009 at 4:49 AM, Ned Batchelder wrote:
>
>> Add the word "core" to make the first sentence, "Discussion group for
>> Django core developers"
On Fri, May 8, 2009 at 4:49 AM, Ned Batchelder wrote:
> Add the word "core" to make the first sentence, "Discussion group for
> Django core developers".
>
Good idea, but I'd take it step farther. "Core" is just ambiguous enough
outside the bubble that some people will still stop reading at the f
Having followed the group here for some time, anybody posting a job
posting or similar off-topic posting tends to be a first time poster,
and in most cases it's very obvious that they never even bothered to
read the group description. That being the case, I think clarifying
the group description
>> """
>> Discussion group for Django developers. This group is used for
>> discussion of developing Django itself, not user questions; Please use
>> django-users for issues regarding using the framework, questions for
>> the Django user community, outreach, etc.
>> """
>>
I agree that all the pe
Hello, I am working on heavy-AJAX-based website and use firebug alot
to check responces from server, in case of 500 error Django sends full
500 page which is not very easy to use. I've made a simple patch to
provide light version of 500 page in case of ajax request.
I know that everybody is in ru
As an alternative, we could try FRAMEWORK for extra emphasis. Perhaps
a bit janky, though.
-justin
On May 8, 2009, at 9:24 AM, Marty Alchin wrote:
>
> On Fri, May 8, 2009 at 7:05 AM, Jacob Kaplan-Moss
> wrote:
>> """
>> Discussion group for Django developers. This group is used for
>> d
Perhaps emphasis on "contributors" rather than "developers"?
J
On Fri, May 8, 2009 at 4:32 PM, Justin Lilly wrote:
>
> As an alternative, we could try FRAMEWORK for extra emphasis. Perhaps
> a bit janky, though.
>
> -justin
>
>
>
> On May 8, 2009, at 9:24 AM, Marty Alchin wrote:
>
>>
>> On Fr
On Fri, May 8, 2009 at 7:05 AM, Jacob Kaplan-Moss
wrote:
> """
> Discussion group for Django developers. This group is used for
> discussion of developing Django itself, not user questions; Please use
> django-users for issues regarding using the framework, questions for
> the Django user communi
On Fri, May 8, 2009 at 1:49 PM, Ned Batchelder wrote:
> Add the word "core" to make the first sentence, "Discussion group for
> Django core developers".
>
> Not that that will make them read the description, but...
>
> --Ned.
>
> Jacob Kaplan-Moss wrote:
>
> On Fri, May 8, 2009 at 12:59 PM, Joshu
Add the word "core" to make the first sentence, "Discussion group for
Django core developers".
Not that that will make them read the description, but...
--Ned.
Jacob Kaplan-Moss wrote:
> On Fri, May 8, 2009 at 12:59 PM, Joshua Partogi wrote:
>
>> Some people get confused and thought that th
On Fri, May 8, 2009 at 12:59 PM, Joshua Partogi wrote:
> Some people get confused and thought that this list is for people that
> develop apps with django :-D
Those people might want to take the time to read the list description
(http://groups.google.com/group/django-developers) that they see wh
Some people get confused and thought that this list is for people that
develop apps with django :-D
On May 6, 11:32 pm, Alex Gaynor wrote:
> 2009/5/6 Yeh, Kenzou K.F.
>
>
>
>
>
> > Hello there,
>
> > Actually i come from Taiwan, and i' m a software engineer.
>
> > i am programmer, used to codin
25 matches
Mail list logo
