One of the issues that needs to be fixed for this is the package name for the code. Currently it's "cqpid", which isn't close to what we have in other languages (which all use a variable on qpid.messaging).
However, we can't use that since it's what our pure Python code uses. Or can we? That's the question: how do we package up the code? I've experimented with the examples we have and they seem to work just fine with cqpid substituted for qpid.messaging for the imports. If our goal is to eventually replace the pure Python with the swigged version, then we could use the same package with a note to users that they need to pick one or the other. This would give us a clear migration path. Ideas? -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
pgplsFloXVJRA.pgp
Description: PGP signature
