--- - branch: MAIN date: Wed Mar 13 18:23:35 UTC 2019 files: - new: '1.19' old: '1.18' path: pkgsrc/net/py-foolscap/distinfo pathrev: pkgsrc/net/py-foolscap/distinfo@1.19 type: modified id: 20190313T182335Z.9131b5800c1c9614da50b467f94e24001b54adf1 log: | py-foolscap: updated to 0.13.1 Release 0.13.1 This release adds a minor feature to "flappclient": it now pays attention to a pair of environment variables named $FOOLSCAP_TOR_CONTROL_PORT and $FOOLSCAP_TOR_SOCKS_PORT. If set, the client will install a connection handler that routes "tor:" -type FURLs through a Tor daemon at the given ports (both of which are endpoint descriptors, e.g. "tcp:localhost:9050"). To use this, install the "tor" extra, like "pip install foolscap[tor]". If this extra was not installed (e.g. "txtorcon" is not importable), the environment variables will be ignored. This release also improves the reliability of the unit test suite (specifically test_reconnector) on slower systems. Release 0.13.0 This release fixes compatibility with the latest Twisted-17.9.0 and changes the way logfiles are encoded. Foolscap's "flogtool" event-logging system can be configured to serialize log events into "Incident Files". In previous versions, these were serialized with the stdlib "pickle" module. However a recent change to Twisted's "Failure" class made them unpickleable, causing Foolscap's unit test suite to fail, and also affect applications which foolscap.logging.log.msg() with Failures as arguments. And untrusted pickles were unsafe to load anyways. This release replaces pickle with JSON, making it safe to use "flogtool" utilities on untrusted incident files. All new incident files created by this version will use JSON, and all tools (e.g. "flogtool dump") can only handle JSON-based files. This also resolves a problem with tox-2.9.0, which caused tests to not run at all because nothing was installed into the test environment. module: pkgsrc subject: 'CVS commit: pkgsrc/net/py-foolscap' unixtime: '1552501415' user: adam