Steve Holden wrote:
> lazaridis_com wrote:
> > Georg Brandl wrote:
> >>lazaridis_com wrote:
> >>>Georg Brandl wrote:
> >>>>lazaridis_com wrote:
> >>>>
> >>>>>I would like to fulfill the following task:
> >>>&
Bruno Desthuilliers wrote:
> lazaridis_com wrote:
> > Bruno Desthuilliers wrote:
> >> lazaridis_com wrote:
> >>> Ο/Η Bruno Desthuilliers έγραψε:
> >>>> lazaridis_com wrote:
> >>>>> John Salerno wrote:
> >>>>>> A
alex23 wrote:
> lazaridis_com wrote:
> > The "persist case" evaluates python persistency systems (or
> > mechanisms), and will show my personal preference:
>
> Do you feel that evaluating-for-evaluation's-sake produces a more
> measured understanding of the
Bruno Desthuilliers wrote:
> lazaridis_com wrote:
> > Ο/Η Bruno Desthuilliers έγραψε:
> >> lazaridis_com wrote:
> >>> John Salerno wrote:
> >>>> Are there any major differences between these two? It seems they can
> >>>> both b
Georg Brandl wrote:
> lazaridis_com wrote:
> > Georg Brandl wrote:
> >> lazaridis_com wrote:
> >> > I would like to fulfill the following task:
> >> >
> >> > The construct:
> >> >
> >> > if __name__ == '__main__
Simon Forman wrote:
> lazaridis_com wrote:
> > I would like to fulfill the following task:
> >
> > The construct:
> >
> > if __name__ == '__main__':
> >
> > should be changed to something like:
> >
> > if identifier.name ==
lazaridis_com wrote:
> lazaridis_com wrote:
> > I would like to change the construct:
> >
> > if __name__ == '__main__':
> ...
>
> Is there a standard way / naming to wrap "__name__" and other similar
> attributes to an encapsulating class
Georg Brandl wrote:
> lazaridis_com wrote:
> > I would like to fulfill the following task:
> >
> > The construct:
> >
> > if __name__ == '__main__':
> >
> > should be changed to something like:
> >
> > if identifier.name == '
I would like to fulfill the following task:
The construct:
if __name__ == '__main__':
should be changed to something like:
if identifier.name == '__main__':
The term "identifier" should be selected based on the meaning of the
__double-underscore-enclosure__ of the entities.
-
What I would ne
Ο/Η Bruno Desthuilliers έγραψε:
> lazaridis_com wrote:
> > John Salerno wrote:
> >> Are there any major differences between these two? It seems they can
> >> both be used with TurboGears, and SQLAlchemy with Django. I'm just
> >> wondering what everyone
John Salerno wrote:
> Are there any major differences between these two? It seems they can
> both be used with TurboGears, and SQLAlchemy with Django. I'm just
> wondering what everyone's preference is, and why, and if there are even
> more choices for ORM.
>
> Thanks.
You can review the Persit Ca
lazaridis_com wrote:
> I would like to change the construct:
>
> if __name__ == '__main__':
...
Is there a standard way / naming to wrap "__name__" and other similar
attributes to an encapsulating class?
Something like e.g.:
if mod.name ...
or
if gbl.name ...
Larry Bates wrote:
> lazaridis_com wrote:
> > I would like to change the construct:
> >
> > if __name__ == '__main__':
> >
> > to something like:
> >
> > if exec.isMain():
> >
> > My (OO thought) is to place a class in an sepa
Duncan Booth wrote:
> lazaridis_com wrote:
>
> > Are ther alternative constructs/mechanism available, which could be
> > used to add this functionality possiby directly to a code-module?
>
> How about something along these lines:
>
> -- auto.py
Fuzzyman wrote:
> lazaridis_com wrote:
> > I would like to change the construct:
> >
> > if __name__ == '__main__':
> >
> > to something like:
> >
> > if exec.isMain():
> >
> > My (OO thought) is to place a class in an separate c
I would like to change the construct:
if __name__ == '__main__':
to something like:
if exec.isMain():
My (OO thought) is to place a class in an separate code module and to
instantiate an singleton instance which would keep th something like
this:
class ExecutionEnv:
def isMain(self)
Colored Code Blocks
Pudge generated documentation can contain colored code blocks, using
the rst directive
"..code-block:: Python" (an other languages supported by SilverCity).
http://pudge.lesscode.org/trac/ticket/21
http://pudge.lesscode.org/trac/changeset/126
-
Mailing List
The Pudge Maili
Colored Code Blocks
Pudge generated documentation can contain colored code blocks, using
the rst directive
"..code-block:: Python" (an other languages supported by SilverCity).
http://pudge.lesscode.org/trac/ticket/21
http://pudge.lesscode.org/trac/changeset/126
-
Mailing List
The Pudge Maili
For a larger scale project, a collaboration infrastructure and toolset
should be selected.
More information about the overall project:
http://lazaridis.com/pj
The actually active system is a Dedicated Server (with Trac & SVN).
A Project Host Candidate which comes close to the needed system is
A
19 matches
Mail list logo