On 2/15/07, Matt Feifarek <[EMAIL PROTECTED]> wrote: > On 2/15/07, Ian Bicking <[EMAIL PROTECTED]> wrote: > > These extra files are about presenting an API to the world that is > > fairly abstract -- mostly the Paste Deploy API. This hides Pylons, and > > even Paste, and makes it easier to deal with your application in an > > abstract manner. > > I don't fully understand all of the ins and outs of that, but I gathered > that it was so... but that's kinda my point. As a custom one-off application > that I write for a client, there won't be anything that wants to deal with > my application as an API, or in an abstract manner... it's not a plugin to > anything, it's just a web site. > > > > This is conflating the directory you put something into with the Python > > package. It makes things like branches awkward, and you can't build on > > tools like workingenv. > > Good point. > > > > Personally I don't think deploy.ini should go in the main package at > > all, though I can understand why people wouldn't want to introduce the > > extra abstraction when they are doing only simple deployments. > > > Another good point... I understand that one of the cool things about those > ini files is that they can be anywhere... but if you KNOW where it is, and > you know where your code is (on sys.path somewhere) you don't really need > this feature. > > For example, if I have something inside of the lib directory of a pylons > app, and I want to get to it from some other bit of python, I currently > can't, since it's not on sys.path. I suppose I could "install" the egg, and > then get to it, but it seems like I now have to do a lot more work (that > feels like "magic" to me) just to get back to standard python behavior. > > > > Well, I'll try to talk you out of it: > > > > You've listed a lot of very nice features, but not things that I really > need... I just want to run a one-off web site here. > > Still, I'll try and adapt my mindset and ignore the files and things that I > don't need or understand. I'm guessing since you didn't say "you can turn > that off like this..." that I can't turn it off. So I'll adapt. > > Thanks for the quick response.
Use "python setup.py develop" and then pretend you're not using an egg, but that you installed the app in Python's site-packages ;) I have multiple one-off Web sites. I just think of eggs as a nice way to distribute them in .zip files :-/ Happy Hacking! -jj -- http://jjinux.blogspot.com/ _______________________________________________ Paste-users mailing list [email protected] http://webwareforpython.org/cgi-bin/mailman/listinfo/paste-users
