On Fri, 2009-08-07 at 08:37 -0700, gruszczy wrote:
> Hi everyone!
>
> I have created a ticket here: http://code.djangoproject.com/ticket/11644,
> but it was marked wontfix and told to ask here about this change.
>
> The issue is that I consider convenient being able to pass a list of
> either tu
On Fri, 2009-08-07 at 20:17 -0700, Marc Garcia wrote:
> Hi Malcolm,
>
> I thought it didn't make sense to close tickets from commits until
> now.
You don't close the ticket. You put "Refs" in the commit message and it
puts the commit message in the ticket without closing. This is all
described i
Hi Malcolm,
I thought it didn't make sense to close tickets from commits until
now. The reason is that I haven't been working ticket by ticket, but
refactoring all the i18n part at the same time, so basically I would
had to close all the tickets on the same commit. That wasn't a good
option in my
On Sat, Aug 8, 2009 at 12:33 AM, Jacob Kaplan-Moss wrote:
>
> On Fri, Aug 7, 2009 at 11:19 AM, Rob Hudson wrote:
>> I'd be happy to help flesh out one or more of these. This isn't
>> necessarily a 1.2 feature but would be a nice addition to the
>> documentation.
>
> I am *always* looking to impro
On Sat, 2009-08-08 at 00:15 +0100, Dougal Matthews wrote:
> I'm a +1 for helping and doing whatever I can do improve the tutorials
> as I think they could be expanded. However I'm about to bugger off for
> a month so I'm not sure how that will fit in with timelines and such.
We are thinking of wa
I'm a +1 for helping and doing whatever I can do improve the tutorials as I
think they could be expanded. However I'm about to bugger off for a month so
I'm not sure how that will fit in with timelines and such.
Dougal
2009/8/7 Jacob Kaplan-Moss
>
> On Fri, Aug 7, 2009 at 11:19 AM, Rob Hudson w
On Fri, Aug 7, 2009 at 11:19 AM, Rob Hudson wrote:
> I'd be happy to help flesh out one or more of these. This isn't
> necessarily a 1.2 feature but would be a nice addition to the
> documentation.
I am *always* looking to improve the docs, so of course I'm an
enthusiastic +1 on more tutorials.
At the end of the 4th step of the tutorial, it lists some tutorials
that are upcoming:
Coming soon
===
The tutorial ends here for the time being. Future installments of the tutorial
will cover:
* Advanced form processing
* Using the RSS framework
* Using the cache framework
On Fri, Aug 7, 2009 at 10:37 AM, gruszczy wrote:
> The issue is that I consider convenient being able to pass a list of
> either tuples or single objects for choices list in forms ChoiceField.
> The engine would itself detect non-tuple values and turn them into two-
> tuples. There are some good p
Hi everyone!
I have created a ticket here: http://code.djangoproject.com/ticket/11644,
but it was marked wontfix and told to ask here about this change.
The issue is that I consider convenient being able to pass a list of
either tuples or single objects for choices list in forms ChoiceField.
The
I agree that this is currently possible in Django, I'm already using
some of what you proposed:
- I've customized add, change and delete permissions of ModelAdmin
to allow a user to manipulate only its own posts;
- I've customized the queryset method to show only the allowed posts
of a user.
On Fri, Aug 7, 2009 at 5:13 PM, Uolter wrote:
>
> What I would like to have in the next Django rel is a better support
> to web services and rest api.
>
> I am using now the django-rest-interface, but I don't find it very
> flexible. For instance I can have the xsd descriptor automatically to
> ex
What I would like to have in the next Django rel is a better support
to web services and rest api.
I am using now the django-rest-interface, but I don't find it very
flexible. For instance I can have the xsd descriptor automatically to
expose to any consumer.
Cheers,
Uolter
--~--~-~-
13 matches
Mail list logo
