On Sun, Jun 5, 2011 at 10:47 AM, Peter Enerccio <[email protected]> wrote:
> If you wanna use pyglet only for one project, you might as well unpack > it to the root of your project, and the imports will work. For the > matter, you can put it anywhere, provided you include it in sys paths. > Of course you *can* do either of those things, but unless one is running a ridiculously non-standard python installation, I don't see any real advantage over installing pyglet wherever your default python installation likes to keep it's packages? The pyglet installer does exactly this for the system python, and for most users I reckon that should work well enough. For the users who have sufficient knowledge of python internals to handle a custom python installation, manually installing pyglet shouldn't be too hard... (hint: pyglet has a standard setuptools installation process). -- Tristam MacDonald System Administrator, Suffolk University Math & CS Department -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
