I have always used ‘python setup.py install’ or msi/exe installers for my python packages in windows
Today I installed Phoenix from the egg file (wxPython_Phoenix-3.0.1.dev75783-py3.3-win32.egg) using easy_install for the first time (first time for both egg and easy_install), so I was not sure what to expect.
Most installed applications in my site-packages have an application folder and an egg-info folder or file.
I have always used 'python setup.py install' or msi/exe installers for
my python packages in windows
Today I installed Phoenix from the egg file
(wxPython_Phoenix-3.0.1.dev75783-py3.3-win32.egg) using easy_install for
the first time (first time for both egg and easy_install), so I was not
sure what to expect.
Most installed applications in my site-packages have an application
folder and an egg-info folder or file.
For example, for scipy I have:
Yes, that is correct for installs made with easy_install. The whole point of eggs was to make things as self-contained as possible, so having everything in one .egg folder (or even in a single .egg file if it doesn't need to be unzipped) is the approach that they took.
Why is it different for all other
packages I have ?
Because they were installed from source (or pip), not as an egg.
Any advantage ?
I think there are advantages and disadvantages to either approach, but they are fairly minor so it doesn't matter a whole lot. I'll be switching to the new wheel packages one of these days and that will be yet another approach to installation, but the end result is more like the "setup.py install" style than the egg style.