`crossbarconnect` Python package

#1

Hello,

Few weeks ago I was implementing some Crossbar.io HTTP Bridge services in a couple of projects. Turned out that the documentation points to a Python package called crossbarconnect that doesn’t seem to exist any more: http://crossbar.io/docs/HTTP-Bridge-Publisher/

Looking around I found this thread commenting the topic, which seems pretty much dead: https://groups.google.com/forum/#!topic/crossbario/6B7SNyFYoWI

Feenes pointed out an actual package that does exactly what the documentation says: https://github.com/thehq/python-crossbarhttp The package was developed by Eric Chapman at The HQ, a company based in L.A. https://thehq.io/

Now, the development of that package was stopped around October 2015 and unfortunately only worked in Python 2. I needed it to work in both Python 2 and 3 versions to use it in a couple of different projects. So I fixed that and I submitted a PR to The HQ repo: https://github.com/thehq/python-crossbarhttp/pull/1

However, they didn’t respond yet to the PR.

At this point, I am thinking on releasing my own package in PyPI if I don’t get a response from them in a reasonable time. Anyway, it is released with a MIT license, so that is entirely possible to do, afaik.

So, my specific question (finally) is: can I name the package as you named the original one, crossbarconnect? If I do this, you don’t have to update the official documentation, since (I think) what it says is covered by Eric Chapman version, and moreover my new code has a couple of extra features. Would I have your (Crossbar.io Team) permission to do this?

In case you agree, I can give you my updated GitHub repo, so you can take ownership of it in your own GitHub account if you prefer that. Also the same will be for the PyPI page in case you finally want it, I can release a new crossbarconnect version and give you guys the admin rights of the package as well.

What do you think about this? Are you interested on it, or should I just release a package on my own, named differently?

Thanks for your time,
Jose

0 Likes

#2

If you want to release on PyPi I think you will find it easiest if you use a new name.

···

On Wednesday, 31 August 2016 22:50:38 UTC+2, José Luis Patiño Andrés wrote:

Hello,

Few weeks ago I was implementing some Crossbar.io HTTP Bridge services in a couple of projects. Turned out that the documentation points to a Python package called crossbarconnect that doesn’t seem to exist any more: http://crossbar.io/docs/HTTP-Bridge-Publisher/

Looking around I found this thread commenting the topic, which seems pretty much dead: https://groups.google.com/forum/#!topic/crossbario/6B7SNyFYoWI

Feenes pointed out an actual package that does exactly what the documentation says: https://github.com/thehq/python-crossbarhttp The package was developed by Eric Chapman at The HQ, a company based in L.A. https://thehq.io/

Now, the development of that package was stopped around October 2015 and unfortunately only worked in Python 2. I needed it to work in both Python 2 and 3 versions to use it in a couple of different projects. So I fixed that and I submitted a PR to The HQ repo: https://github.com/thehq/python-crossbarhttp/pull/1

However, they didn’t respond yet to the PR.

At this point, I am thinking on releasing my own package in PyPI if I don’t get a response from them in a reasonable time. Anyway, it is released with a MIT license, so that is entirely possible to do, afaik.

So, my specific question (finally) is: can I name the package as you named the original one, crossbarconnect? If I do this, you don’t have to update the official documentation, since (I think) what it says is covered by Eric Chapman version, and moreover my new code has a couple of extra features. Would I have your (Crossbar.io Team) permission to do this?

In case you agree, I can give you my updated GitHub repo, so you can take ownership of it in your own GitHub account if you prefer that. Also the same will be for the PyPI page in case you finally want it, I can release a new crossbarconnect version and give you guys the admin rights of the package as well.

What do you think about this? Are you interested on it, or should I just release a package on my own, named differently?

Thanks for your time,
Jose

0 Likes

#3

Hi Jose,

sorry for the late answer - and thanks for chipping in with your own efforts!

We would prefer it if you released the package yourself and under a name which references crossbar but makes it clear that this is not provided by us. Once you’ve done so, could you drop me a line or post here so that I can add the repo & package to the docs?

Regards,

Alex

···

Am Mittwoch, 31. August 2016 22:50:38 UTC+2 schrieb José Luis Patiño Andrés:

Hello,

Few weeks ago I was implementing some Crossbar.io HTTP Bridge services in a couple of projects. Turned out that the documentation points to a Python package called crossbarconnect that doesn’t seem to exist any more: http://crossbar.io/docs/HTTP-Bridge-Publisher/

Looking around I found this thread commenting the topic, which seems pretty much dead: https://groups.google.com/forum/#!topic/crossbario/6B7SNyFYoWI

Feenes pointed out an actual package that does exactly what the documentation says: https://github.com/thehq/python-crossbarhttp The package was developed by Eric Chapman at The HQ, a company based in L.A. https://thehq.io/

Now, the development of that package was stopped around October 2015 and unfortunately only worked in Python 2. I needed it to work in both Python 2 and 3 versions to use it in a couple of different projects. So I fixed that and I submitted a PR to The HQ repo: https://github.com/thehq/python-crossbarhttp/pull/1

However, they didn’t respond yet to the PR.

At this point, I am thinking on releasing my own package in PyPI if I don’t get a response from them in a reasonable time. Anyway, it is released with a MIT license, so that is entirely possible to do, afaik.

So, my specific question (finally) is: can I name the package as you named the original one, crossbarconnect? If I do this, you don’t have to update the official documentation, since (I think) what it says is covered by Eric Chapman version, and moreover my new code has a couple of extra features. Would I have your (Crossbar.io Team) permission to do this?

In case you agree, I can give you my updated GitHub repo, so you can take ownership of it in your own GitHub account if you prefer that. Also the same will be for the PyPI page in case you finally want it, I can release a new crossbarconnect version and give you guys the admin rights of the package as well.

What do you think about this? Are you interested on it, or should I just release a package on my own, named differently?

Thanks for your time,
Jose

0 Likes

#4

Hi Alex,

Many thanks for the reply.

I understand the point. I finished packaging my fork this morning and released it to PyPI: https://pypi.python.org/pypi/crossbarhttp3

Mentions to Eric and The HQ are done in the fork, and the license remains the same (MIT). Just now is compatible with Python versions 2.6 (sic, there are a bunch of systems that are still using this stuff out there), 2.7, 3.4 and 3.5, which can be checked here: https://travis-ci.org/jose-lpa/crossbarhttp3

Two new optional features were added to the client as well: timeout, which lets the developer to set a time out for idle requests, and silently, which makes the client return None for any failing request, instead of raising an exception. Anyways, the default behavior remains the same as it was in the old fork. Documentation can be checked in GitHub https://github.com/jose-lpa/crossbarhttp3 for more references.

Thank you again, and let me know if you need anything else :slight_smile:

Regards,
Jose

···

El jueves, 8 de septiembre de 2016, 12:21:31 (UTC+1), Alexander Gödde escribió:

Hi Jose,

sorry for the late answer - and thanks for chipping in with your own efforts!

We would prefer it if you released the package yourself and under a name which references crossbar but makes it clear that this is not provided by us. Once you’ve done so, could you drop me a line or post here so that I can add the repo & package to the docs?

Regards,

Alex

Am Mittwoch, 31. August 2016 22:50:38 UTC+2 schrieb José Luis Patiño Andrés:

Hello,

Few weeks ago I was implementing some Crossbar.io HTTP Bridge services in a couple of projects. Turned out that the documentation points to a Python package called crossbarconnect that doesn’t seem to exist any more: http://crossbar.io/docs/HTTP-Bridge-Publisher/

Looking around I found this thread commenting the topic, which seems pretty much dead: https://groups.google.com/forum/#!topic/crossbario/6B7SNyFYoWI

Feenes pointed out an actual package that does exactly what the documentation says: https://github.com/thehq/python-crossbarhttp The package was developed by Eric Chapman at The HQ, a company based in L.A. https://thehq.io/

Now, the development of that package was stopped around October 2015 and unfortunately only worked in Python 2. I needed it to work in both Python 2 and 3 versions to use it in a couple of different projects. So I fixed that and I submitted a PR to The HQ repo: https://github.com/thehq/python-crossbarhttp/pull/1

However, they didn’t respond yet to the PR.

At this point, I am thinking on releasing my own package in PyPI if I don’t get a response from them in a reasonable time. Anyway, it is released with a MIT license, so that is entirely possible to do, afaik.

So, my specific question (finally) is: can I name the package as you named the original one, crossbarconnect? If I do this, you don’t have to update the official documentation, since (I think) what it says is covered by Eric Chapman version, and moreover my new code has a couple of extra features. Would I have your (Crossbar.io Team) permission to do this?

In case you agree, I can give you my updated GitHub repo, so you can take ownership of it in your own GitHub account if you prefer that. Also the same will be for the PyPI page in case you finally want it, I can release a new crossbarconnect version and give you guys the admin rights of the package as well.

What do you think about this? Are you interested on it, or should I just release a package on my own, named differently?

Thanks for your time,
Jose

0 Likes