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 <[email protected]> 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 <[email protected]> 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:[email protected] >> >> > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
