On Sep 20, 8:19 am, Peng Yu wrote:
>
> I am wondering what is the best way of organizing python source code
> in a large projects. There are package code, testing code. I'm
> wondering if there has been any summary on previous practices.
>
(Sorry for the late reply.)
My advice: Don't write big p
On 20 Sep., 22:10, exar...@twistedmatrix.com wrote:
> On 07:10 pm, pengyu...@gmail.com wrote:
>
> >On Sun, Sep 20, 2009 at 11:31 AM, Daniel Fetchinson
> > wrote:
> >>>I am wondering what is the best way of organizing python source code
> >>>in a large projects. There are package code, testing code.
On 07:10 pm, pengyu...@gmail.com wrote:
On Sun, Sep 20, 2009 at 11:31 AM, Daniel Fetchinson
wrote:
I am wondering what is the best way of organizing python source code
in a large projects. There are package code, testing code. I'm
wondering if there has been any summary on previous practices.
On Sun, Sep 20, 2009 at 11:31 AM, Daniel Fetchinson
wrote:
>> I am wondering what is the best way of organizing python source code
>> in a large projects. There are package code, testing code. I'm
>> wondering if there has been any summary on previous practices.
>
> I suggest looking at the source
> I am wondering what is the best way of organizing python source code
> in a large projects. There are package code, testing code. I'm
> wondering if there has been any summary on previous practices.
I suggest looking at the source code of large projects like twisted,
PIL, django, turbogears, etc
Hi,
I am wondering what is the best way of organizing python source code
in a large projects. There are package code, testing code. I'm
wondering if there has been any summary on previous practices.
Regards,
Peng
--
http://mail.python.org/mailman/listinfo/python-list
