Brainstorming

Distribution/Handling? dependencies

• One option which was the first idea was to check for commons libraries used based on scanning sourcefiles for import statements, then just copying the directory over as necessary.

Wouldn't it be better to add an option to export a "manifest"? such as Commons::using('foo'); Commons::using('bar'); Commons::dumpManifest(); and it creates a list from the stuff that has been imported so far? That definitely sounds more fool proof, requires less work, and would make packaging super easy. -- noccy

Sounds good for PHP, but it would make things a tad weird on Python, not to mention implicit imports are generally considered bad practice for Python. On second thought, do we really need that kind of automation? Why not just a script, f.ex, commons-init --using=net.protocols,io.parsers --exclude=net.protocols.irc,io.parsers.csv --template SomeProject --directory .? -- miniman

Structure

This should be language agnostic. Localized language rules should be applied afterwards, such as for JS: io.parsers.Csv. Consistency is key -- noccy

• io
  • parsers
    • csv
    • xml
    • ical
    • vcard
• net
  • protocols
    • irc
    • http
    • xmpp
    • ldap
• core
  • local
    • datetime
    • timezones
  • utils/tools
  • async

perhaps things like decorators (like cached_property from miniature) should go in core.utils? and event handler and queue primitives or such in core.async?

Comment by noccy on Mon Oct 19 02:18:43 2009

local should probably have a better name...

Comment by miniman on Mon Oct 19 16:47:12 2009

locale perhaps?

Error: Macro AddComment(None) failed

Error: Insufficient privileges to AddComment