[Dev] place for utility classes/functions?
bear at code-bear.com
Tue Apr 26 10:20:54 PDT 2005
+1 to chandler/utils/
Open Source Applications Foundation (OSAF)
PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
On Apr 26, 2005, at 1:02 PM, Morgen Sagen wrote:
> Yep, I agree with Heikki that tools should be for scripts outside of
> chandler, and something like "util" should be for helper modules. So
> tools/timing.py (if it's still useful) would be moved to
> On Apr 26, 2005, at 9:57 AM, Heikki Toivonen wrote:
>> I would vote against tools in this case. IMO tools is something that
>> not needed by Chandler itself when it is running, but some external
>> scripts (maybe tweak repo outside of Chandler or something).
>> Unfortunately we already have chandler/tools folder that contains
>> required to run Chandler itself - I'd vote to move that elsewhere once
>> we decide where that should be.
>> I think Alec's examples would rather go into chandler/util(s), or
>> chandler/lib(s) or something like that - neither of which we have yet.
>> Mike Taylor wrote:
>>> In the past python only code like that has been placed in
>>> On Apr 26, 2005, at 12:01 PM, Alec Flett wrote:
>>> So I've been poking around with the Python Cookbook and found a
>>> recipes that are vastly simplifying my code... (namely
>>> CachedAttribute and frange, which does floating-point
>>> ranges) and I have a few of my own (CopyOnWrite, etc)
>> Heikki Toivonen
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>> Open Source Applications Foundation "Dev" mailing list
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "Dev" mailing list
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20050426/8f8f183b/PGP.pgp
More information about the Dev