search

bcdev / jpy

A bi-directional Python-Java bridge used to embed Java in CPython or the other way round.
Apache License 2.0
187 stars 37 forks source link

WHL files for Python 3.7 #168

Open eLvErDe opened 5 years ago

eLvErDe commented 5 years ago

Hello,

Are you planning to release WHL files for Python 3.7 ?

Thanks in advance,

Adam.

forman commented 5 years ago

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 commented 5 years ago

@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 commented 5 years ago

@forman : do you have any interest in having Deephaven take an active role in maintaining jpy and producing artifacts?

ShaheedHaque commented 5 years ago

@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 commented 5 years ago

@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 commented 5 years ago

@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 commented 5 years ago

Cool. Let's see what @forman says in terms your kind offer.

forman commented 5 years ago

@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.

ShaheedHaque commented 5 years ago

@forman any updates please?

ShaheedHaque commented 4 years ago

@forman any update on the proposal from @devinrsmith?

JamesXNelson commented 3 years ago

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 commented 3 years ago

@JamesXNelson - I believe we've started a discussion amongst our teams. Please check in w/ @chipkent

pont-us commented 3 years ago

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.

forman commented 3 years ago

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!