> -> /home/pmcnett/dabo > top level dabo directory, the one with AUTHORS and README and (most > importantly) the one with the dabo subdirectory (the top-level of the > importable dabo stuff).
So you have /home/pmcnett/dabo/dabo right? That bothers me. so does dabo/dabo/dabo, which is what I had for a while, then I switched to dabo/trunk/dabo/dabo, which I don't like either. -> /home/pmcnett/dabo -> /home/pmcnett/daboide -> /home/pmcnett/ss I think you are going to find your home to become cluttered. Even if works for you, I don't feel good recommending it. > somewhere and importable from Python. It matters not where individuals > choose to place their directories, true, the docs should make that clear. > and I'd argue that part of the > process of initiation into something like Dabo would be for people to > come up with their own best practices themselves. It isn't rocket science. > So we should just replace the docs with "you figure it out." ? :) The day that someone installs Dabo is not the day they should be figuring this kind of thing out. Good chance they are overwhelmed with things to figure out, and having a suggested path to follow really helps. Even for seasoned python programmers, the concept of some abstract classes may be new (I bet most are use to working with modules) and a seperate dir of tools (like ide) may also be new. It certainly isn't the normal set of things you get with anything I have seen. But thanks for your vote, and the explanations. Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
