JEmbed is coming along beautifully.
For more information, please check out the blog at http://jpype.blogspot.com/
It's been way too long in coming, but JPype is not dead!
It is, however changing name to JEmbed. More info on this as it matures.
I will try and bundle together a minor release of JPype 0.5 in the coming weeks.
I've added a blog entry on JPype's blog where people can leave their experiences with Jpype. If you've succesfully used JPype in one of your projects, or were completely unable to, please visit http://jpype.blogspot.com/2006/09/jpype-success-and-horror-stories.html and leave your comments!
I;ve created a blog for JPype at http://jpype.blogspot.com
There I will try to document the history and the continuing improvement to JPype.
Just wanted to clarify : libgcj support will be in ADDITION to JNI support, not replace it.
I've started work on version 0.6. However, unlike previously announced, subclassing will not be the focus of the release.
Rather, I am redesigning (again) the java postability layer to contain less C++. In so doing, I am hoping to achieve :
- More stability
- Support for Ruby
- Support for libGCJ instead of JNI.
- A foundation better suited to future extensions.
Efforts will be made to maintain backward compatibility. However, in the interest of moving forward and improving things, some features may change or be dropped.
Recent increases in work/domestic demands mean I haven't had as much time as I'd like to work on JPype ... rest assured the project is not dead ... merely delayed.
After quite a pause, 0.5 is now ready for testing.
0.5 is another major step forward. It fixes quite a few bugs, and introduces many new features.
The only problem at this moment is lack of documentation. I will be focusing on a new set of documenttion on the next few weeks, hopefully even drafting a person I know who writes tech documents for a living to at least review my drafts, perhaps more. IN the meantime, 0.5 is 100% backward compatibvle with 0.4, so the 0.4 doscs, as they are, are still usable.
I am very happy to say that JPype now compiles and run under MacOSX!
Thanks to Dan Sandler for sending me the required code changes. According to him it passes the 'hello world' test.
Since the change didnt require any c-level changes, I can be failry confident future releases will not break it, although I am not in a position to verify each releases.
Starting with version 0.4.2, I will provide Binary installer for both Python 2.3 and python 2.4.
Starting with 0.4.1, I will not be bale to provide linux binaries for i386. My personal system recently got upgraded to AMD64 and I have no access at the moment to a suitable system to build the binary packages.
Futher, "straight" binary packages (non-installer and non-rpm) will no longer be distributed. Distutil would hard-coded my python installation;s directory, which was bad for most people. The Python team advises it is better to use the installer or RPM packages.... read more
At user request, I have create a Users mailing list for JPype.
Simply go to http://lists.sourceforge.net/lists/listinfo/jpype-users to subscribe.
JPype seems to have problem when used interactively. After calling startJVM, python will report SyntaxErrors for everything that comaes afterward. Fortunately, this seems to affect only interacttive prompt as regular script execution without without problem.