On Sun, May 24, 2009 at 4:44 PM, Alan Gauld <alan.ga...@btinternet.com> wrote:
> "Michael Bernhard Arp Sørensen" <mich...@arpsorensen.dk> wrote
> Most folks get by with the standard libraryb and a small number of
> specialist modules to meet their specific needs. If you need a new
> one install it, but loading lots of stuff just because its there is just a
> waste of disk space IMHO.
>
>> create my own python repo to set up a good working environment for
>> development. That way I could use any distro.
>
> By defaulyt Python keeps all its installed packages in the Python
> directory structure so, effectively, you do build up your own repo. But
> don't do it in advance just add to it as you need to.
>
>> On the other hand, any code I might write would be difficult
>> for others to use.
>
> If you stick to the a standard Python package tools it should be fine.
> Not just on Linux but on any other OS too.
>
>
> --
> Alan Gauld
> Author of the Learn to Program web site
> http://www.alan-g.me.uk/

I agree with Alan. These days the trend seems to be in the opposite direction.

I'm seeing developers keeping a "clean" Python environment and then
installing additional packages into virtual environments. That keeps
conflicts to a minimum and solves the problem of uninstalling unwanted
packages.

http://pypi.python.org/pypi/virtualenv

Some developers even go so far as putting their Python environment
under version control using something like Bazaar, git, or Mercurial
(alphabetical order). This is in an effort to keep the contents of
their Python environment under control.

Once you have setuptools installed, it just too easy to type
"easy_install spam" and get that package installed into your
environment. The challenge is to control clutter in your environment.

http://pypi.python.org/pypi/setuptools

If you can keep your dependencies under control, then you can give
users a reasonable set of requirements. If necessary, you can bundle
things up for end users:

http://www.py2exe.org/
http://svn.pythonmac.org/py2app/py2app/trunk/doc/index.html
http://pypi.python.org/pypi/zc.buildout

On the other hand, I do believe that Python needs an expanded distro
for developers, but it would only contain a few extra things, such as
the items mentioned above.

-- 
Walker Hale <walker.hale...@gmail.com>
_______________________________________________
Tutor maillist  -  Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor

Reply via email to