Re: [Py4j-users] New intermediate release of Py4J
Status: Beta
Brought to you by:
barthe
From: Jason Ni <jas...@gm...> - 2012-07-23 10:02:55
|
Got it. Thank you. 在 2012-7-23 下午5:14,"Barthelemy Dagenais" <ba...@cs...>写道: > Hi, > > The version number is still 0.7 because this is just a temporary build and > it is only available through github (but it's the same kind of file that is > available on sourceforge and you can download it by clicking on the "raw" > button). The final release will be 0.8 and will be available on pypi and > sourceforge. > > Barthélémy > > On 2012-07-23, at 3:27 AM, Jason Ni wrote: > > > Great job! Thanks a lot! > > What's the version number of this release? Will this release replace the > 0.7 package in the sourceforge download page? > > > > 2012/7/22 Barthelemy Dagenais <ba...@cs...> > > Hi, > > > > I just built a new release of py4j that includes a few fixes: > > > > 1. long types are now correctly converted (issue #99). Please note that > > Python 3 merged int and long. This means that Py4J has to do all the > > inference work on the Java side for Python 3. In some corner cases, Py4J > > might not be able to call the method you want (e.g., you have > > method1(int) and method1(long) and you are calling from python 3 > > method1(123). method1(int) will be called even though you may want > > method1(long) to be called. The only workaround I can think of is to > > create an adapter in Java and call this adapter). > > > > 2. decimals are now supported and correctly converted (issue #101) > > > > 3. plugged memory leak in GatewayServer when multiple python clients > > were connecting and disconnecting (java side, discussed on this mailing > > list last week) > > > > 4. gateway.close() (python side) now correctly sends a close signal to > > the java side (discovered while testing fix for #3) > > > > 5. by default, the python and java sides now try to connect to 127.0.0.1 > > instead of localhost. It is always possible to specify an address when > > instantiating a JavaGateway and a GatewayServer. > > > > The release is available in the current-release directory: > > https://github.com/bartdag/py4j/tree/master/current-release > > > > It has been tested on python 2.7 and 3.2 and on Java 1.6. The full 0.8 > > release will be tested on python 2.6, 2.7, 3.1, and 3.2. > > > > Barthélémy > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > Py4j-users mailing list > > Py4...@li... > > https://lists.sourceforge.net/lists/listinfo/py4j-users > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ > > Py4j-users mailing list > > Py4...@li... > > https://lists.sourceforge.net/lists/listinfo/py4j-users > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Py4j-users mailing list > Py4...@li... > https://lists.sourceforge.net/lists/listinfo/py4j-users > |