You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 5, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 5, 2021. It is now read-only.
@eLvErDe : my company (https://deephaven.io/) is maintaining a fork of jpy https://github.com/illumon-public/illumon-jpy. We have released 3.7 wheels, see https://pypi.org/project/deephaven-jpy/#files. Our release is a significant number of commits ahead of bcdev/jpy/master (and not yet reflected in our own master branch yet - we've got a bit of CI work on our internal servers and coordination that we need to do regarding releases, tags, and branches wrt our product version).
@devinrsmith I'm really glad you are actively maintaining a fork, and it would be great to see "official" new wheels for Linux 3.6 etc. up on pypi. (Aside: I wonder why illumon-jpy does not appear in the list of forks here...)
@ShaheedHaque : I wasn't originally responsible for our fork, so it might have been setup as an "unofficial" fork outside of the github fork mechanism. Definitely something I'll look into as we more formally establish our fork for public consumption. In the meantime - we do have newer 3.6 wheels :) - although, it doesn't look like the linux ones have been published to PyPi - I'll look into that.
@forman : do you have any interest in having Deephaven take an active role in maintaining jpy and producing artifacts?
@devinrsmith yes, thanks, we are definitely interested in contributions. However, we need to make sure that the evolution of jpy is still supporting our main use case, namely the beckend of the bidi Java-Python bridge snappy for our software project SNAP which we develop for the European Space Agency.
I'm going to discuss your possible future role with the SNAP team, then I come back to you shortly.
Deephaven continues to actively develop and maintain jpy. If SNAP is willing to test our archives to ensure they are compatible, we can formalize our release process to include merging code upstream. We are in the process of open sourcing part of our product, and are developing a new release process for our jpy wheels. If there was a good time to consider handing off release management, that time would be now.
If there was a good time to consider handing off release management, that time would be now.
@forman suggests a meeting to discuss this and I have created a Doodle poll to find a suitable time in the near future. Doodle poll link. Suggested slots should work for @forman, @marpet, and me -- hopefully one will also be OK for @JamesXNelson , @devinrsmith , @chipkent , and any other interested parties.
If SNAP is willing to test our archives to ensure they are compatible, we can formalize our release process to include merging code upstream.
@JamesXNelson that sounds great. Lets dicuss our collaboration further. From the doodle, earliest possible date for @devinrsmith, @marpet, @pont-us any myself is Wednesday May 5, 14:00-15:00 CET. Let's go for it!
Activity
forman commentedon May 14, 2019
I'd like to, but currently have no project / spare time to do so.
Note that you can also build wheels on your own.
devinrsmith commentedon May 15, 2019
@eLvErDe : my company (https://deephaven.io/) is maintaining a fork of jpy https://github.com/illumon-public/illumon-jpy. We have released 3.7 wheels, see https://pypi.org/project/deephaven-jpy/#files. Our release is a significant number of commits ahead of bcdev/jpy/master (and not yet reflected in our own master branch yet - we've got a bit of CI work on our internal servers and coordination that we need to do regarding releases, tags, and branches wrt our product version).
devinrsmith commentedon May 15, 2019
@forman : do you have any interest in having Deephaven take an active role in maintaining jpy and producing artifacts?
ShaheedHaque commentedon May 17, 2019
@devinrsmith I'm really glad you are actively maintaining a fork, and it would be great to see "official" new wheels for Linux 3.6 etc. up on pypi. (Aside: I wonder why illumon-jpy does not appear in the list of forks here...)
devinrsmith commentedon May 17, 2019
@ShaheedHaque : I wasn't originally responsible for our fork, so it might have been setup as an "unofficial" fork outside of the github fork mechanism. Definitely something I'll look into as we more formally establish our fork for public consumption. In the meantime - we do have newer 3.6 wheels :) - although, it doesn't look like the linux ones have been published to PyPi - I'll look into that.
devinrsmith commentedon May 17, 2019
@ShaheedHaque : we have linux wheels available from our GitHub release page - https://github.com/illumon-public/illumon-jpy/releases. I've inquired about getting them published to PyPi as well - thanks!
ShaheedHaque commentedon May 17, 2019
Cool. Let's see what @forman says in terms your kind offer.
forman commentedon May 20, 2019
@devinrsmith yes, thanks, we are definitely interested in contributions. However, we need to make sure that the evolution of jpy is still supporting our main use case, namely the beckend of the bidi Java-Python bridge snappy for our software project SNAP which we develop for the European Space Agency.
I'm going to discuss your possible future role with the SNAP team, then I come back to you shortly.
ShaheedHaque commentedon Jul 10, 2019
@forman any updates please?
ShaheedHaque commentedon Feb 16, 2020
@forman any update on the proposal from @devinrsmith?
JamesXNelson commentedon Apr 23, 2021
Deephaven continues to actively develop and maintain jpy. If SNAP is willing to test our archives to ensure they are compatible, we can formalize our release process to include merging code upstream. We are in the process of open sourcing part of our product, and are developing a new release process for our jpy wheels. If there was a good time to consider handing off release management, that time would be now.
devinrsmith commentedon Apr 23, 2021
@JamesXNelson - I believe we've started a discussion amongst our teams. Please check in w/ @chipkent
pont-us commentedon Apr 27, 2021
@forman suggests a meeting to discuss this and I have created a Doodle poll to find a suitable time in the near future. Doodle poll link. Suggested slots should work for @forman, @marpet, and me -- hopefully one will also be OK for @JamesXNelson , @devinrsmith , @chipkent , and any other interested parties.
forman commentedon Apr 30, 2021
@JamesXNelson that sounds great. Lets dicuss our collaboration further. From the doodle, earliest possible date for @devinrsmith, @marpet, @pont-us any myself is Wednesday May 5, 14:00-15:00 CET. Let's go for it!