+1 to Jonathan's approach.
Giving the reader the opportunity to compare and contrast a
one-file app to a packaged app--while discussing a reasoned
approach to packaging--would be a huge help to folks new to Python.
I also recommend pointing out where things specifically pertain
either to Pyramid or Python, giving a context of where to look
for more information.
Modifying Paul's list:
- Do a single-file Hello World
- Make the single-file app into a Python distribution
- "BTW, Pyramid comes with things called 'scaffolds'. A
scaffold in programming of applications serves a similar purpose
to a scaffold in construction of buildings. Scaffolds do all
that we did in the previous steps with a single command.
Shweeeeet." Then use a scaffold.
- Add in pserve with an INI file
- Then, off to the races
On a personal note, if it wasn't for the sage guidance about
Python that I've received from Pyramid folks, I might not have
picked up Python.
--steve
On 9/2/13 at 11:37 AM, [email protected] (Jonathan Vanasco) pronounced:
What if you start it and show as a single-file then - instead
of throwing it out - convert the same to a package ?
i.e. --
first 30% - here's pyramid basics. it's so simple we only need
a single file.
last 70% - typical pyramid projects can be dozens of files.
let's convert our code to a package, using a ___ scaffold.
the github docs could also have 3 examples that people can reference:
- the 1 file app ( finished up to the transition point )
- the package app ( the end version, and also finished up to
the end of the tutorial )
------------------------
Steve Piercy, Soquel, CA
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
