En Sun, 25 May 2008 19:46:50 -0300, Casey McGinty <[EMAIL PROTECTED]> escribió:
> On Sat, May 24, 2008 at 2:11 PM, Gabriel Genellina <[EMAIL PROTECTED]>
> wrote:
>
>> > 2. In the top of your package directory it is typical to have a module
>> name
>> > '_package.py'. This is ideally where the main
On Sat, May 24, 2008 at 2:11 PM, Gabriel Genellina <[EMAIL PROTECTED]>
wrote:
> > 2. In the top of your package directory it is typical to have a module
> name
> > '_package.py'. This is ideally where the main command line entry point
> for
> > the package code should be placed.
>
> Why the unders
En Wed, 21 May 2008 07:44:50 -0300, Casey McGinty <[EMAIL PROTECTED]> escribió:
Just my own opinion on these things:
> 1. Script code should be as basic as possible, ideally a module import line
> and function or method call. This is so you don't have to worry about script
> errors and/or increas
> I'm starting work on what is going to become a fairly substantial
> Python project, and I'm trying to find the best way to organize
> everything.
I'd like to add a follow up question. Are there any idioms for writing
/usr/bin scripts to run installed package modules? For this I am assuming a
s
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| Hello all,
|
| I'm starting work on what is going to become a fairly substantial
| Python project, and I'm trying to find the best way to organize
| everything. The project will consist of:
|
| - A few applications
| - Several small sc
A.T.Hofkamp wrote:
> Also, why do you make a distinction between shared and non-shared code?
> You could simply eliminate 'shared' directory, and put its contents
> directly under myproject.
I would go further and make them individual projects, with their own version
control, code repository and
On 2008-05-19, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I'm starting work on what is going to become a fairly substantial
> Python project, and I'm trying to find the best way to organize
> everything. The project will consist of:
>
> - A few applications
> - Several small scri
Hello all,
I'm starting work on what is going to become a fairly substantial
Python project, and I'm trying to find the best way to organize
everything. The project will consist of:
- A few applications
- Several small scripts and utilities
- Unit tests and small interactive test programs
- A num
