Russell Keith-Magee wrote:
>
> On 31/03/2008, at 2:33 AM, mtrier wrote:
>
>> Before opening a ticket I thought I would check what the expected
>> behavior is for generative values(). This is the behavior I'm seeing
>> on Queryset Refactor branch and to me it seems like it is not the
>> correct
On Wed, Apr 2, 2008 at 7:06 PM, msaelices <[EMAIL PROTECTED]> wrote:
> Now, what do you see? You first think again in a form with two fields,
> however maybe is a form with five fields. What is happening? You
> explicity define two fields, and the real action is a _redefinition_
> of two field
This mail maybe can be splitted in two, but I write only one because
both are related.
Ok, ModelForms is a very very wonderful thing, but I want to talk
about (maybe) excessive implicitness.
Look at this form declaration:
class AuthorForm(forms.Form):
name = myforms.MyCharField(max_length=1
> Once the refactor is complete we can start looking at writing new stuff.
Sorry, posted my last message before seeing this.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this
> While I agree with the importance of having reusability tips, I would
> certainly argue against putting it anywhere near django.contrib. When
> I started working on my first app, I had unnecessary delusions of
> getting into django.contrib when it was ready. I wouldn't want to
> cause more peopl
On Wed, Apr 2, 2008 at 5:58 PM, SmileyChris <[EMAIL PROTECTED]> wrote:
> I'd suggest moving install to a how-to rather than a topical guide.
> Perhaps deployment could go under there, too? They seem closely
> related.
So the idea is that "topics" are for focused, core topical guides;
"how-tos"
On Wed, Apr 2, 2008 at 6:05 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> One thing that struck me while looking over this list is that it might
> be a good idea to add a section on best practices for writing reusable
> apps. James Bennett's presentation at PyCon hit on some really good
>
On Wed, Apr 2, 2008 at 7:05 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> One thing that struck me while looking over this list is that it might
> be a good idea to add a section on best practices for writing reusable
> apps. James Bennett's presentation at PyCon hit on some really good
>
Looks really good--a lot cleaner and better laid out than the current
docs!
One thing that struck me while looking over this list is that it might
be a good idea to add a section on best practices for writing reusable
apps. James Bennett's presentation at PyCon hit on some really good
main point
I'd suggest moving install to a how-to rather than a topical guide.
Perhaps deployment could go under there, too? They seem closely
related.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
T
Hi folks --
I've finished making a new outline for the documentation based on my
proposal I posted last week. It's available online:
HTML: http://toys.jacobian.org/django/new-docs-outline/
OPML: http://toys.jacobian.org/django/new-docs-outline.opml
OmniOutliner: http://toys.jacobian.
On Tue, 2008-04-01 at 08:58 -0700, Jason Ledbetter wrote:
> I'm looking for feedback on my SoC application which I call
> "Effortless Model Testing". EMT would add sample instance generation,
> fuzz testing, and (if still necessary) model-level validation to
> Django.
>
> I have my ideas explain
Is there a quick and easy way to the get to the newly added object
when overriding the save_add method?
(Other than having to sort by the primary key and picking the first
item, which might not always be dependable...)
--~--~-~--~~~---~--~~
You received this mess
On Wed, Apr 2, 2008 at 4:42 PM, David Larlet <[EMAIL PROTECTED]> wrote:
>
> Le 2 avr. 08 à 02:09, [EMAIL PROTECTED] a écrit :
>
> >
> >
> > Models in Django are conceputally based on tables in a database. I'd
> > like to enhance that with the introduction of resource-based models.
> > The basi
On Wed, Apr 2, 2008 at 10:47 AM, AmanKow <[EMAIL PROTECTED]> wrote:
> Will the api and internals references be generated (at least in part)
> via doc string extraction? That's a big plus to me.
When appropriate we could; Sphinx does that, too:
http://sphinx.pocoo.org/ext/autodoc.html
Like Jam
On Wed, Apr 2, 2008 at 12:22 PM, James Bennett <[EMAIL PROTECTED]> wrote:
> I most sincerely hope not; unless you're like me and write short-form
> novels in your docstrings, they tend to be an absolutely horrible
> source of end-user documentation.
def get_object_from_cache(self, ...):
""
On Wed, Apr 2, 2008 at 10:47 AM, AmanKow <[EMAIL PROTECTED]> wrote:
> Will the api and internals references be generated (at least in part)
> via doc string extraction? That's a big plus to me.
I most sincerely hope not; unless you're like me and write short-form
novels in your docstrings, the
Will the api and internals references be generated (at least in part)
via doc string extraction? That's a big plus to me.
On Mar 31, 2:45 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> I'm embarking on a mission to refactor Django's documentation; this is where
> you give me feedback about
I am also extremely interested. This is exactly what I need for a
project I'm currently working on and one I may be working on for this
year's SoC.
Let me know if it gets accepted - I'd love to discuss it with you and
I can help test.
Thanks
Ben
On 2 Apr 2008, at 01:09, [EMAIL PROTECTED]
We've set up a group for participants in django's GSoC:
http://groups.google.com/group/django-gsoc
If you are a mentor, or potential student participant, please join the
group so that we can discuss GSoC-related topics there.
Regards,
Mark Choate
--~--~-~--~~~---~--~
Le 2 avr. 08 à 02:09, [EMAIL PROTECTED] a écrit :
>
>
> Models in Django are conceputally based on tables in a database. I'd
> like to enhance that with the introduction of resource-based models.
> The basic idea comes from Ruby on Rails' ActiveResource, which allows
> for interaction between two
21 matches
Mail list logo
