pEpPythonAdapter/releases

Releases

Final Releases

2.1.3

Component Git rev. hash Rel. Tag
pEpPythonAdapter 8623adce030bb929e929bec5210ea4e94e104f15 2.1.3
libpEpAdapter 1270d1476e5e401210ef7eb1a708d7cf8029c8e5 Release_2.1.17
pEpEngine c6cd6b02dc18c980e8fe7ed36bf4211054d85c3e Release_2.1.23
Sequoia 365d00a08bec6a5a48d48a7c7893d78c27092b59 not tagged
Changelog
  • FEATURE: PYADPT-110 - Add Mutlithreaded Sync Implementation
  • TEST: PYADPT-110: Update sync testing (sync_handshake.py) to work with new sync impl
  • TEST: PYADPT-110: Add a test for start_sync() / stop_sync() repeatedly

2.1.2

Component Git rev. hash Rel. Tag
pEpPythonAdapter 3c9bcc19784d6d8c870a4263c183b2b15ec9f4fb 2.1.2
libpEpAdapter 1270d1476e5e401210ef7eb1a708d7cf8029c8e5 Release_2.1.17
pEpEngine c6cd6b02dc18c980e8fe7ed36bf4211054d85c3e Release_2.1.23
Sequoia 365d00a08bec6a5a48d48a7c7893d78c27092b59 not tagged
Changelog
  • CI: Add DEPENDENCIES file
  • DOCS: improve README.rst

2.1.1

Component Git rev. hash Rel. Tag
pEpPythonAdapter c9864de24e982c6e419ff346c0c009a3423ff7d8 2.1.1
libpEpAdapter c732f24c48b66733aad0e5292deff87ba6229ee4 Release_2.1.6
pEpEngine 6af7aa85782f7d588a2d9bfcc25d6389b4f1c276 Release_2.1.13
Sequoia 365d00a08bec6a5a48d48a7c7893d78c27092b59 not tagged
Changelog
  • Add Windows project and adjust build script for Windows build
  • Overhaul install instructions
  • Impoved general project structure
  • Improved Makefile (every operation needs make target)
  • provide venv setup make target (LD_LIB etc..)
  • Obtain pkg version from git (setuptools_scm)
  • Changed Rel tag format from e.g. “Release_2.1.1” to just “2.1.1” for setuptools compatibility
  • Added pytest as testframework
  • started writing a test suite
  • PYADPT-97 - Use sphynx for documentation
  • Added more documentation
  • PYADPT-98 - Fix pytests created with old pEp version
  • PYADPT-99 - Add more pytests to test message ecrypt modifies the original message
  • PYADPT-86 - “Rename native_pEp into _pEp” PYADPT-89 - “Make native_pep / _pEp a submodule of pEp” More doc
  • PYADPT-87 - “Drop usless __main__ part form module”
  • PYADPT-100 - “pytest: subprocess per test required”
  • AGPL 3.0 headers everywhere
  • Update author credits

Release Candidates

About This Docuement

 heck> | 1) Which engine version should be specified if the adapter supports a whole range of versions?
 fdik> | 1) the latest engine darthmama recommends to use
 heck> | 2) what if there is a new engine version but no new adapter version ( New engine func needed, but no change in adapter required) ?
 fdik> | 2) you add a new version always even if nothing changed
 heck> | 3) only direct deps of the adapter ? (like libpEpAdapter, pEpEngine), OR the full stack of deps and deps of deps...??? (like which version of rust to compile sequoia?, etc... )
 fdik> | 3) full stack
 heck> | 4) how far back do i need to documet the releases? from now on? or all regressively all rels there have ever been?
 fdik> | 4) from now on beginning what needs to be used now
 heck> | 5) for patch rels of adapter, is the correct engine versio to be used always latest of this minor release like 2.1.<highest-available> ?
 fdik> | 5) => darthmama decides
 heck> | if its full stack, i think its almost unavoidable that dependency info needs to be published of each component recursively down the tree.
 heck> | So, in other words, pEpEngine will need to publish their rel infos (deps) for each rel
 heck> | sequoia will have to provide that too, etc...
 heck> | its a dependency tree...
 heck> | in which every component inherits all dependencies from all its children
 heck> | or did you imagine a different sort of approach to the problem...
 heck> | ?
 fdik> | see the provided example page