your program logic is, and yes, terse but easy to
understand ways of doing things like loops and functional programming
methods, and that are extended by modules or packages with a well-defined
interface, can let you focus on the program at higher levels that do fit in
your memory and can be reasoned
27;m newbie toZopeand i have a few questions regarding external
> >>> methods. What i wan't to do
> >>> is provide a terse syntax for converting urls to special tracking
> >>> urls:
> >>> http://myurl/')">
> >>> turns t
Jens schrieb:
> On Jan 25, 3:19 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
>> Jens schrieb:
>>
>>
>>
>>> Hello Everyone
>>> I'm newbie to Zope and i have a few questions regarding external
>>> methods. What i wan
Jens a écrit :
> On Jan 25, 3:19 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
>> Jens schrieb:
>>
>>
>>
>>> Hello Everyone
>>> I'm newbie to Zope and i have a few questions regarding external
>>> methods.
(snip)
>>> This doesn't work because because the method doesn't have access to
>>> the e
On Jan 25, 3:19 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> Jens schrieb:
>
>
>
> > Hello Everyone
>
> > I'm newbie to Zope and i have a few questions regarding external
> > methods. What i wan't to do
> > is provide
Jens schrieb:
> Hello Everyone
>
> I'm newbie to Zope and i have a few questions regarding external
> methods. What i wan't to do
> is provide a terse syntax for converting urls to special tracking
> urls:
>
> http://myurl/')">
>
> turns
Hello Everyone
I'm newbie to Zope and i have a few questions regarding external
methods. What i wan't to do
is provide a terse syntax for converting urls to special tracking
urls:
http://myurl/')">
turns the provided url into something like
http://host/tracking?url=ht
Roy> Is there any way to make the traceback printer built into the
Roy> interpreter elide all the directories in pathnames (like
Roy> strip_dirs() does for the profiler)?
There's a compact traceback printer in asyncore (compact_traceback). I used
it as the basis for a compact stack p
Is there any way to make the traceback printer built into the
interpreter elide all the directories in pathnames (like strip_dirs()
does for the profiler)?
I'm working in a deep directory tree, and the full pathnames to my
python source files are pushing 150 characters. I either need a
laptop wit
