> Thanks, Kay. Of course, the workaround would be better known if the
> setuptools web page had those instructions instead of "install using
> the [non-existent] .exe file." :-)
The instructions were written before Python 2.6 was released. They
haven't be updated since.
Regards,
Martin
--
http:
On Apr 16, 11:52 am, Kay Schluehr wrote:
> Yes, but there is a known workaround:
Thanks, Kay. Of course, the workaround would be better known if the
setuptools web page had those instructions instead of "install using
the [non-existent] .exe file." :-)
--
http://mail.python.org/mailman/lis
Mac schrieb:
We've got ActiveState Python 2.6 installed on a Windows XP box, and I
pulled down the latest archgenxml package (2.2) in order to get it
running under this installation of Python. I unpacked the tarball for
the package and tried running `python setup.py build' but got an
ImportError
On 16 Apr., 17:39, Mac wrote:
> We've got ActiveState Python 2.6 installed on a Windows XP box, and I
> pulled down the latest archgenxml package (2.2) in order to get it
> running under this installation of Python. I unpacked the tarball for
> the package and tried running `python setup.py build
We've got ActiveState Python 2.6 installed on a Windows XP box, and I
pulled down the latest archgenxml package (2.2) in order to get it
running under this installation of Python. I unpacked the tarball for
the package and tried running `python setup.py build' but got an
ImportError exception: "no
