On 28 sep, 17:32, Thomas Weholt wrote:
> Inspired by the discussions in this thread I've created a reusable app
> that mainly consists of a couple of management commands, like
> startbigapp ( working name ) which is a crude hack of the startapp
> code in django. It
A small feature suggestion for @All,
Please address with @ symbol and name if you are actually intending
someone to read,
and then please delete the already existing message in your reply.
That makes us poor people to read things clearly and make up something
out of important discussions like
Inspired by the discussions in this thread I've created a reusable app
that mainly consists of a couple of management commands, like
startbigapp ( working name ) which is a crude hack of the startapp
code in django. It creates module for models and views instead of the
standard views.py and
Seems to be a general ferment on the topics of reusable Django apps
and best practices for modularizing large projects.
For example,
http://groups.google.com/group/django-users/browse_thread/thread/22875fd287d0aa81
I expect the situation to improve, or at least change, a lot over the
next year.
On 28 sep, 10:02, Benedict Verheyen
wrote:
> I agree with Thomas that at least some guidelines would be nice.
> As what you and Steve have been saying about the need for a "Python for
> Djangonauts" class,
> i think it would be a good idea also.
> I'm wondering
On 28/09/2010 0:48, bruno desthuilliers wrote:
>
>
> On 27 sep, 17:31, Thomas Weholt wrote:
>> On Mon, Sep 27, 2010 at 4:52 PM, bruno desthuilliers
>>
>
>>> ??? Which "django specific magic" ???
>>
>> I was referring to syncdb. As far as I know, models defined outside
On 27/09/2010 23:59, Diederik van der Boor wrote:
> SInce watching that video, my projects are composed by default of 2 apps. A
> "projectname" for the core backend stuff, and a "projectname-site" with the
> templates, settings, and frontend media. This is imho a nicer base to start
>
Op maandag 27 september 2010 09:08:53 schreef MrMuffin:
> Where do you put your business logic in django? In my project I`ve put
> it into the models.py, but that file soon become huge and hard to
> maintain. Of course I can just stuff it into whatever file I like, but
> I`d like to have some
On 27 sep, 17:31, Thomas Weholt wrote:
> On Mon, Sep 27, 2010 at 4:52 PM, bruno desthuilliers
>
>> ??? Which "django specific magic" ???
>
> I was referring to syncdb. As far as I know, models defined outside
> any models.py or models module won`t be picked up by
On 9/27/2010 11:31 AM, Thomas Weholt wrote:
> On Mon, Sep 27, 2010 at 4:52 PM, bruno desthuilliers
> wrote:
>> On 27 sep, 12:55, Thomas Weholt wrote:
>>> On Mon, Sep 27, 2010 at 12:40 PM, Steve Holden wrote:
I
Hello,
The following is quite long but reflects a non developper point of view.
I'll expose briefly that business analysis already splits logic and why
I think you should follow previous recommandations. I'll finish "out of
subject" commenting your documentation request.
> Split business
On Mon, Sep 27, 2010 at 4:52 PM, bruno desthuilliers
wrote:
> On 27 sep, 12:55, Thomas Weholt wrote:
>> On Mon, Sep 27, 2010 at 12:40 PM, Steve Holden wrote:
>> > I think the point is to learn enough Python that you
On 27 sep, 12:55, Thomas Weholt wrote:
> On Mon, Sep 27, 2010 at 12:40 PM, Steve Holden wrote:
> > I think the point is to learn enough Python that you don't need
> > Django-specific advice.
>
> > [Thinks: definitely time for a "Python for
On Mon, Sep 27, 2010 at 12:40 PM, Steve Holden wrote:
> On 9/27/2010 4:57 AM, Thomas Weholt wrote:
>> On Mon, Sep 27, 2010 at 10:38 AM, bruno desthuilliers
>> wrote:
>>> On 27 sep, 09:08, MrMuffin wrote:
Where do
On 9/27/2010 4:57 AM, Thomas Weholt wrote:
> On Mon, Sep 27, 2010 at 10:38 AM, bruno desthuilliers
> wrote:
>> On 27 sep, 09:08, MrMuffin wrote:
>>> Where do you put your business logic in django?
>>
>> Depends on the definition of
On 27 sep, 10:57, Thomas Weholt wrote:
> Ok, I see your point, but still - there`s nothing about this in the
> main django documentation as far as I know. The docs should have a
> section about organizing projects where the standard models.py and
> views.py doesn`t fit
On 09/27/10 09:57, Thomas Weholt wrote:
> On Mon, Sep 27, 2010 at 10:38 AM, bruno desthuilliers
> wrote:
>> Using the package's __init__.py as a facade is certainly not "hackish"
>> - it's one of - if not the main - the raison d'être of this file.
>>
>> Now if your
On 27/09/2010 9:08, MrMuffin wrote:
> Where do you put your business logic in django? In my project I`ve put
> it into the models.py, but that file soon become huge and hard to
> maintain. Of course I can just stuff it into whatever file I like, but
> I`d like to have some standard way of doing
On Mon, Sep 27, 2010 at 10:38 AM, bruno desthuilliers
wrote:
> On 27 sep, 09:08, MrMuffin wrote:
>> Where do you put your business logic in django?
>
> Depends on the definition of "business logic", but :
>
>> In my project I`ve put
>> it
On 27 sep, 09:08, MrMuffin wrote:
> Where do you put your business logic in django?
Depends on the definition of "business logic", but :
> In my project I`ve put
> it into the models.py,
That's also what I tend to do for anything that's not a pure utility
class or
On Mon, Sep 27, 2010 at 10:07 AM, Mike Dewhirst wrote:
> On 27/09/2010 5:08pm, MrMuffin wrote:
>>
>> Where do you put your business logic in django? In my project I`ve put
>> it into the models.py, but that file soon become huge and hard to
>> maintain. Of course I can just
On 27/09/2010 5:08pm, MrMuffin wrote:
Where do you put your business logic in django? In my project I`ve put
it into the models.py, but that file soon become huge and hard to
maintain. Of course I can just stuff it into whatever file I like, but
I`d like to have some standard way of doing this.
Sometimes I put it in some 'utils.py' in the app directory, and sometimes in
'views.py' itself, with leading underscores, whichever I feel is more
appropriate.
I guess this would be more of the developer's choice. Any better
suggestions?
Thanks,
Subhranath Chunder.
On Mon, Sep 27, 2010 at 12:43
2010/9/27 MrMuffin :
> Where do you put your business logic in django? In my project I`ve put
> it into the models.py, but that file soon become huge and hard to
> maintain. Of course I can just stuff it into whatever file I like, but
> I`d like to have some standard way
24 matches
Mail list logo