Prepare packaging (zest)

[AntoineCezar]

Extracted from issue #17

[kiorky]

related commits :
2f98d9d 03fae7d 694e173

[AntoineCezar]

Great job ! I have just one concern : does the buildout flow needs to break the pyramid flow ? (I've never used buildout)

[kiorky]

What are you calling pyramid flow !?

[AntoineCezar]

I mean not having to learn buildout in a pyramid project.
Is there a way to keep the pyramid standard files and folder structure ?

[kiorky]

The only missing files are dev.ini and prod.ini which are generated now via buildout, i readded regenerated ones in b43dd69
There is no others changes in the distribution.

[ghost]

It really looks like all those buildout boilerplate files don't belong to the project's main source code repository. Seeing things like "apache" in the source code raises a clear sign that this doesn't follow the SoC principle.

Committing an empty var directory seems a bit odd. Surely this can be created when needed. This is why this practice is not supported by git, hence the .empty file hack.

Is there any added value in burying the source code under two levels of directories? I understand that creating the src subdirectory might be motivated by separating application source code from buildout boilerplate files (see my first point), but why src/convertit?

More generally speaking, what would buildout add to the project at this point? Buildout is great for managing non-Python dependencies, but if it's not used that way yet, what's the motivation for using it?

My feeling is that buildout is too intrusive to be hardcoded in the project and I don't see at this point any benefit in introducing tight coupling between a deployment tool and the application source code.

[kiorky]

I ll not go in any debate just do no press the merge button if you dont understand the sense of sain commits.
Just burn your wings with some namespaces issues with top level directories in develop mode and you ll never forget to package correctly your distributions with a inner top level directory.

[kiorky]

btw, i just subscribed out notifications, just speak to @leplatrem for anything else.