Development situation

[Rémi Rampin]

Hi,

First of all, thanks for a great piece of software. jnius is definitely useful to anyone trying to use Java together with Python, and I definitely see myself using it in the near future.

However, the current situation is a little bit confusing. What I see is:

• The project is called "pyjnius". It is mentioned in the README, and it is also the name of the Github repository (kivy/pyjnius) and the ReadTheDocs site.
• The package name (for import from Python) is jnius
• This is fine so far, and pretty common for Python project, however...
• The PyPI entry is "jnius", not "pyjnius" (correct me if I'm wrong). This IMHO warrants a link in the README file
• There is a different, separately-maintained entry "pyjnius" on PyPI. As far as I know, this is physion's, however there is no mention on this on PyPI, it still points to your repository and ReadTheDocs site (only the version numbers don't match). Can you confirm this has nothing to do with you?
• Your project, kivy/pyjnius, is still developed. In fact, the current master has important fixes: I couldn't even install the released version on Mac OS. But the latest version on PyPI, 1.0.2, is nearly 3 years old!

It seems a shame to have completely non-code-related issues getting in the way of people using your software. All of that can probably be fixed easily, so I was wondering if you could perhaps:

• Confirm the previous info; this is all pretty confusing but hopefully I got this right
• Add a link to the PyPI entry in the README
• Do a new release and upload to PyPI, at least to help Mac users. I see that pyjnius has binaries but jnius does not, this might be something I can help you with.

Let me know if there's anything I can do.

Merci d'avance

-- 

Rémi @remram44 Rampin

[Amirouche Boubekki]

On Sun, Apr 26, 2015 at 6:27 PM Rémi Rampin <remir...@gmail.com> wrote:

Hi,

First of all, thanks for a great piece of software. jnius is definitely useful to anyone trying to use Java together with Python, and I definitely see myself using it in the near future.

It's definitly a great project, based on my naive benchmarks it's the fastest Python JNI bindings. What do you want to do?

 

However, the current situation is a little bit confusing. What I see is:

• The project is called "pyjnius". It is mentioned in the README, and it is also the name of the Github repository (kivy/pyjnius) and the ReadTheDocs site.
• The package name (for import from Python) is jnius
• This is fine so far, and pretty common for Python project, however...
• The PyPI entry is "jnius", not "pyjnius" (correct me if I'm wrong). This IMHO warrants a link in the README file
• There is a different, separately-maintained entry "pyjnius" on PyPI. As far as I know, this is physion's, however there is no mention on this on PyPI, it still points to your repository and ReadTheDocs site (only the version numbers don't match). Can you confirm this has nothing to do with you?
• Your project, kivy/pyjnius, is still developed. In fact, the current master has important fixes: I couldn't even install the released version on Mac OS. But the latest version on PyPI, 1.0.2, is nearly 3 years old!

It's difficult to install with easyinstall or pip anyway. On most people using pyjnius have a dev setup. That's why there seem to be a lake of love in this regard.

 

It seems a shame to have completely non-code-related issues getting in the way of people using your software. All of that can probably be fixed easily, so I was wondering if you could perhaps:

• Confirm the previous info; this is all pretty confusing but hopefully I got this right

about pypi jnius: Most of the time, pypi entries get the name of the python package. So, it's correct to have jnius as a pypi entry. There are other patterns but in context of pyjnius, it's a nice choice.
 

• Add a link to the PyPI entry in the README

 Given the fact there is wild (?) entry, it would be good idea. Here, is stub:


-------8<-------------------------------8<-------------------------------8<------------------------

To install pyjnius for Python2 ou Ubuntu (tested with 14.04) you need to install Cython, JDK & JRE {need Python2 headers?}. You can use the following command:

    sudo apt-get install default-jre default-jdk cython

NB: As of 14.04 default-[jre , jdk] installs openjdk

Then use ``pip install`` or ``easyinstall``:

    easyinstall jnius

-------8<-------------------------------8<-------------------------------8<------------------------

It installs correctly and tests works with 1.0.2 tag. matster doesn't work. I attached logs.

• Do a new release and upload to PyPI, at least to help Mac users. I see that pyjnius has binaries but jnius does not, this might be something I can help you with.

 

Let me know if there's anything I can do.

Making it work on MacOs :)))

 

Merci d'avance

Br

-- 

Rémi @remram44 Rampin

[Rémi Rampin]

2015-04-27 6:48 EDT, Amirouche Boubekki <amirouche...@gmail.com>:

It's difficult to install with easyinstall or pip anyway. On most people using pyjnius have a dev setup. That's why there seem to be a lake of love in this regard.

Installing jnius as part of the setup for a bigger project needn't be painful. Of course, you always need the dependencies, but then there is no reason for pip to fail.

about pypi jnius: Most of the time, pypi entries get the name of the python package. So, it's correct to have jnius as a pypi entry. There are other patterns but in context of pyjnius, it's a nice choice.

PyPI entries usually get the name of the project; it's just that most of the time, the name of the project is the package name. Cf pyOpenSSL (package: OpenSSL), pysendfile (module: sendfile), pyBarcode (package: barcode), pyguacamole (package: guacamole) (but of course, looking for projects that are py-something NOT on PyPI is harder, so my list only goes one way).

It installs correctly and tests works with 1.0.2 tag. matster doesn't work. I attached logs.

That's weird, I get the exact opposite behavior. 1.0.2 looks for lib/amd64/server, which is definitely wrong. master builds without problem (didn't even have to set JDK_HOME or JRE_HOME), although the tests don't run (classpath issues, maybe I'm running them wrong).

Let me know if there's anything I can do.

Making it work on MacOs :)))

I'll try and look into that.

[Barry Wark]

On Sunday, April 26, 2015 at 12:27:29 PM UTC-4, Rémi Rampin wrote:

Hi,

First of all, thanks for a great piece of software. jnius is definitely useful to anyone trying to use Java together with Python, and I definitely see myself using it in the near future.

However, the current situation is a little bit confusing. What I see is:

• The project is called "pyjnius". It is mentioned in the README, and it is also the name of the Github repository (kivy/pyjnius) and the ReadTheDocs site.
• The package name (for import from Python) is jnius
• This is fine so far, and pretty common for Python project, however...
• The PyPI entry is "jnius", not "pyjnius" (correct me if I'm wrong). This IMHO warrants a link in the README file
• There is a different, separately-maintained entry "pyjnius" on PyPI. As far as I know, this is physion's, however there is no mention on this on PyPI, it still points to your repository and ReadTheDocs site (only the version numbers don't match). Can you confirm this has nothing to do with you?

Correct. We (Physion) forked pyjnius to pull in build and deployment-related changes as well as some features we needed. Our intention is to push back upstream. Our apologies for the confusion. I will update the PyPI entry to clarify the situation.

Barry