You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Kerry Bonin <ke...@gmail.com> on 2010/06/16 19:22:24 UTC
Python egg support ?
One of the teams using QPID here uses Python, and is looking at
updating to a more recent version of the code to keep in sync with
those of us working in C++ on the Windows platforms.
I was informed this morning that some changes have been made that make
it difficult to generate a "python egg" using the current code. Can
someone from the Python side of the house point me to any information
on how they can use the latest code in a Python application currently
based on "EasyInstall" and "eggs" ?
Thanks...
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Python egg support ?
Posted by Rafael Schloming <ra...@redhat.com>.
Kerry Bonin wrote:
> OK, he tried again with latest. According to him, the bdist egg
> command was removed, and what is generated by default (the
> ...egg-info) is script data to allow a local install, but no egg is
> actually generated. We need to know how to generate an actual egg so
> we can redistribute that, not the entire qpid build tree. Does that
> make sense ?
The bdist_egg command isn't something we provide, it's part of
setuptools. Our setup scripts use distutils by default (which doesn't
include bdist_egg), however you could try using our setup scripts with
setuptools if you like:
http://bob.pythonmac.org/archives/2006/01/18/using-setuptools-features-with-distutils-scripts/
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Python egg support ?
Posted by Kerry Bonin <ke...@gmail.com>.
Just had another talk with the Python lead. He is generating eggs
now, and they work fine on Mac and Ubuntu, but are failing on Windows
somewhere in the xml spec parsing. According to him the 'egg' is a
common enough delivery medium for Python that he's surprised this
wasn't caught in an existing unit test. I've created QPID-2676 and
attached our updated setup.py that works with and without setuptools
and was used to generate the egg which failed on Windows.
On Thu, Jun 17, 2010 at 5:57 AM, Rafael Schloming <ra...@redhat.com> wrote:
> Kerry Bonin wrote:
>>
>> Follow up comment from another Python developer here, abbreviated (I'm
>> not the best filter here since I'm more of a C++/Java/Cg/Lua
>> developer, have only briefly touched Python.)
>>
>> - setup.py is based on disttools, which predates eggs
>> - simple fix would be to change setup.py to use setuptools instead.
>> - recommended fix is to change setup.py to use 'distribute'
>> - Reference link:
>>
>> http://www.mcguru.net/download/presentations/michipug-2006-02-02-Intro-to-setuptools.pdf
>>
>> Another Python developer here just told me he's made the setuptools
>> change to setup.py in our local fork, I'll generate a patch and attach
>> to a JIRA as soon as he checks his changes in.
>
> I'm happy to add optional support for setuptools if there is a clean way to
> do that. I would like to keep the scripts working with distutils as well
> though since that is available by default on any python install without
> having to get additional packages. Give me a ping when you post your JIRA
> and I'll have a look.
>
> --Rafael
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Python egg support ?
Posted by Rafael Schloming <ra...@redhat.com>.
Kerry Bonin wrote:
> Follow up comment from another Python developer here, abbreviated (I'm
> not the best filter here since I'm more of a C++/Java/Cg/Lua
> developer, have only briefly touched Python.)
>
> - setup.py is based on disttools, which predates eggs
> - simple fix would be to change setup.py to use setuptools instead.
> - recommended fix is to change setup.py to use 'distribute'
> - Reference link:
> http://www.mcguru.net/download/presentations/michipug-2006-02-02-Intro-to-setuptools.pdf
>
> Another Python developer here just told me he's made the setuptools
> change to setup.py in our local fork, I'll generate a patch and attach
> to a JIRA as soon as he checks his changes in.
I'm happy to add optional support for setuptools if there is a clean way
to do that. I would like to keep the scripts working with distutils as
well though since that is available by default on any python install
without having to get additional packages. Give me a ping when you post
your JIRA and I'll have a look.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Python egg support ?
Posted by Kerry Bonin <ke...@gmail.com>.
Follow up comment from another Python developer here, abbreviated (I'm
not the best filter here since I'm more of a C++/Java/Cg/Lua
developer, have only briefly touched Python.)
- setup.py is based on disttools, which predates eggs
- simple fix would be to change setup.py to use setuptools instead.
- recommended fix is to change setup.py to use 'distribute'
- Reference link:
http://www.mcguru.net/download/presentations/michipug-2006-02-02-Intro-to-setuptools.pdf
Another Python developer here just told me he's made the setuptools
change to setup.py in our local fork, I'll generate a patch and attach
to a JIRA as soon as he checks his changes in.
On Wed, Jun 16, 2010 at 3:42 PM, Kerry Bonin <ke...@gmail.com> wrote:
> OK, he tried again with latest. According to him, the bdist egg
> command was removed, and what is generated by default (the
> ...egg-info) is script data to allow a local install, but no egg is
> actually generated. We need to know how to generate an actual egg so
> we can redistribute that, not the entire qpid build tree. Does that
> make sense ?
>
> On Wed, Jun 16, 2010 at 2:11 PM, Kerry Bonin <ke...@gmail.com> wrote:
>> I just talked to him - his install aborts with an error, but he was
>> using an older working copy, we'll update (with our patches to c++
>> side) and retry, thanks...
>>
>>
>>
>> On Wed, Jun 16, 2010 at 12:44 PM, Rafael Schloming <ra...@redhat.com> wrote:
>>> Kerry Bonin wrote:
>>>>
>>>> One of the teams using QPID here uses Python, and is looking at
>>>> updating to a more recent version of the code to keep in sync with
>>>> those of us working in C++ on the Windows platforms.
>>>>
>>>> I was informed this morning that some changes have been made that make
>>>> it difficult to generate a "python egg" using the current code. Can
>>>> someone from the Python side of the house point me to any information
>>>> on how they can use the latest code in a Python application currently
>>>> based on "EasyInstall" and "eggs" ?
>>>
>>> All the python code uses distutils which I believe will generate eggs by
>>> default. I don't use eggs myself, so I haven't tried firsthand. Do you have
>>> anymore details on what the issue might be?
>>>
>>> --Rafael
>>>
>>>
>>> ---------------------------------------------------------------------
>>> Apache Qpid - AMQP Messaging Implementation
>>> Project: http://qpid.apache.org
>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>
>>>
>>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Python egg support ?
Posted by Kerry Bonin <ke...@gmail.com>.
OK, he tried again with latest. According to him, the bdist egg
command was removed, and what is generated by default (the
...egg-info) is script data to allow a local install, but no egg is
actually generated. We need to know how to generate an actual egg so
we can redistribute that, not the entire qpid build tree. Does that
make sense ?
On Wed, Jun 16, 2010 at 2:11 PM, Kerry Bonin <ke...@gmail.com> wrote:
> I just talked to him - his install aborts with an error, but he was
> using an older working copy, we'll update (with our patches to c++
> side) and retry, thanks...
>
>
>
> On Wed, Jun 16, 2010 at 12:44 PM, Rafael Schloming <ra...@redhat.com> wrote:
>> Kerry Bonin wrote:
>>>
>>> One of the teams using QPID here uses Python, and is looking at
>>> updating to a more recent version of the code to keep in sync with
>>> those of us working in C++ on the Windows platforms.
>>>
>>> I was informed this morning that some changes have been made that make
>>> it difficult to generate a "python egg" using the current code. Can
>>> someone from the Python side of the house point me to any information
>>> on how they can use the latest code in a Python application currently
>>> based on "EasyInstall" and "eggs" ?
>>
>> All the python code uses distutils which I believe will generate eggs by
>> default. I don't use eggs myself, so I haven't tried firsthand. Do you have
>> anymore details on what the issue might be?
>>
>> --Rafael
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Python egg support ?
Posted by Kerry Bonin <ke...@gmail.com>.
I just talked to him - his install aborts with an error, but he was
using an older working copy, we'll update (with our patches to c++
side) and retry, thanks...
On Wed, Jun 16, 2010 at 12:44 PM, Rafael Schloming <ra...@redhat.com> wrote:
> Kerry Bonin wrote:
>>
>> One of the teams using QPID here uses Python, and is looking at
>> updating to a more recent version of the code to keep in sync with
>> those of us working in C++ on the Windows platforms.
>>
>> I was informed this morning that some changes have been made that make
>> it difficult to generate a "python egg" using the current code. Can
>> someone from the Python side of the house point me to any information
>> on how they can use the latest code in a Python application currently
>> based on "EasyInstall" and "eggs" ?
>
> All the python code uses distutils which I believe will generate eggs by
> default. I don't use eggs myself, so I haven't tried firsthand. Do you have
> anymore details on what the issue might be?
>
> --Rafael
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Python egg support ?
Posted by Rafael Schloming <ra...@redhat.com>.
Kerry Bonin wrote:
> One of the teams using QPID here uses Python, and is looking at
> updating to a more recent version of the code to keep in sync with
> those of us working in C++ on the Windows platforms.
>
> I was informed this morning that some changes have been made that make
> it difficult to generate a "python egg" using the current code. Can
> someone from the Python side of the house point me to any information
> on how they can use the latest code in a Python application currently
> based on "EasyInstall" and "eggs" ?
All the python code uses distutils which I believe will generate eggs by
default. I don't use eggs myself, so I haven't tried firsthand. Do you
have anymore details on what the issue might be?
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org