Hi, all.
I would like to point out a few facts that prompted me to raise the
question of maintaining or dropping Python at the recent development
meeting.
1. The OpenSRF and Evergreen Python libraries are compatible with Python
2.7.
2. Python 2.7 is end of life as of January 1, 2020:
Laurentian is still using the Python bindings to sync users from our LDAP
directory to our library system.
I believe it is also required for any library using Syrup Reserves?
Due to other commitments, I cannot commit to becoming a maintainer of the
Python code at this point in time,
Hi Ken,
The /osrf-gateway-v1 endpoint provides a layer of abstraction over the
OpenSRF XMPP innards, where the chunking/bundling happens. If you continue
using that endpoint, you'll be fine without it.
-b
On Mon, Feb 11, 2019 at 1:35 PM Ken Cox wrote:
> Bill, thanks for mentioning that. I
Bill, thanks for mentioning that. I don't know anything about bundling or
chunking so I am quite certain my fork doesn't have them. Are these
features required when called via osrf-gateway-v1, and where are they
described?
Ken
On Mon, Feb 11, 2019 at 12:22 PM Bill Erickson wrote:
> Thanks,
Hi,
Similar to the question Jason Stephenson asked about the Java bindings [1],
I would like to know if anybody is actively using OpenSRF's and Evergreen's
Python binding.
I do know that the Python binding is a bit less dusty than the Java
binding, as srfsh.py does still work. I also know that
Thanks, Jason.
It's also worth mentioning the Java OpenSRF libs are missing some
new features (bundling/chunking/etc.), so in addition to updating the
dependencies, any prospective maintainer would need to port these features
over to make the Java OpenSRF libs compatible with modern OpenSRF.
-b
Hi,
We will be performing maintenance on the community Git server (
git.evergreen-ils.org) this week to upgrade its operating system. The
maintenance will take place on Tuesday, 12 February starting at 8 a.m. EST
and on Thursday, 14 February starting at 8 a.m. EST.
There will be outages of both
