Hi,
I have an year of experience working in python and django.
I am looking for some projects in django for remote work.
Regards,
Nitin Kumar
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop
hello
i'm trying to develop a multilingual web app with django. i've
acchieved making django translate the messages in the views.py but it
does not translate the messages in the template files.
my message file for English is:
#: html/anasayfa.html:9
#, fuzzy
msgid "Hatali Giris"
msgstr "Not Auth
e an year of experience working in python and django.
> I am looking for some projects in django for remote work.
>
> Regards,
> Nitin Kumar
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this gr
ivas,
> thammanen...@gmail.com
>
>
>
> On Wednesday, January 16, 2019 at 1:31:01 PM UTC+5:30, Nitin Kumar wrote:
>>
>> Hi,
>>
>> I have an year of experience working in python and django.
>> I am looking for some projects in django for remote work.
>&g
On Sat, 2008-01-26 at 04:40 -0800, halukdogan wrote:
> hello
>
> i'm trying to develop a multilingual web app with django. i've
> acchieved making django translate the messages in the views.py but it
> does not translate the messages in the template files.
> my message file for English is:
>
>
On Jan 26, 2008 10:40 AM, halukdogan <[EMAIL PROTECTED]> wrote:
>
> hello
>
> i'm trying to develop a multilingual web app with django. i've
> acchieved making django translate the messages in the views.py but it
> does not translate the messages in the template files.
> my message file for Englis
litting views and models
> into seperate files is only a partial solution and that requires some
> hackish code in __init__.py to make syncdb etc work. And then there`s
> urls.py.
>
> Should there be a better and standardized way to organize huge
> projects in django?
>
> Thanks f
y soon gets huge and how do you
> > re-organize your project when that happens? Splitting views and models
> > into seperate files is only a partial solution and that requires some
> > hackish code in __init__.py to make syncdb etc work. And then there`s
> > urls.py.
into seperate files is only a partial solution and that requires some
hackish code in __init__.py to make syncdb etc work. And then there`s
urls.py.
Should there be a better and standardized way to organize huge
projects in django?
I hope some dguru answers this because it is important.
I reckon
`s
>> urls.py.
>>
>> Should there be a better and standardized way to organize huge
>> projects in django?
>
> I hope some dguru answers this because it is important.
>
> I reckon business rules should be in models.py because that represents the
> database and I'
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 function and that's not strict
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 into the models.py,
>
> That's also what I tend to do for
happens? Splitting views and models
> into seperate files is only a partial solution and that requires some
> hackish code in __init__.py to make syncdb etc work. And then there`s
> urls.py.
>
> Should there be a better and standardized way to organize huge
> projects in django?
&
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 app is really growing that big,
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 anymore.
FWIW, the first s
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 "business logic", but :
>>
>>> In my project I`ve put
>>> it into
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 you put your business logic in django?
>>>
>>> Depends on the definition of "b
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 Djangonauts" class].
>
> I`m asking for a best-practice a
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 don't need
>> > Django-specific advice.
>>
>> > [Thinks: definitely time for a "
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 lo
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 think the point is to learn enough Python that you don't need
Django-specifi
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 syncdb, but I
> might be wrong.
gic and models.
> Should there be a better and standardized way to organize huge
> projects in django?
Yes. Making multiple applications. I highly recommend watching this DjangoCon
video by James Bennett: http://www.youtube.com/watch?v=A-S0tqpPga4
It explains how apps can be made r
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
> "hooking
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
>> any models.py or models
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 though what specific Python topics
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.
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 models.
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 thes
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 creates module for models and vi
30 matches
Mail list logo
