Test under all py2_pickle{1,2,3} and py3_pickle3 ZODB kinds + fix discovered issues
Hello @jerome, For ZODB/go and WCFS, in order to support Python3 and Python2 with recent ZODB5, I need to extend generated test databases to cover all ZODB kinds instead of only ZODB/py2 + pickle protocol=2 we had before. This resulted in `run_with_all_zodb_pickle_kinds` utility inside gen_testdata.py and zodbtools also becoming well tested under all kinds of ZODB databases: py2: ZODB 4 and ZODB5 < 5.3 (pickle protocol 1) py2: ZODB 5.3 (pickle protocol 2) py2: ZODB ≥ 5.4 (pickle protocol 3) py3: ZODB4 and ZODB5 (pickle protocol 3) Please find the patches that do that for zodbtools attached. Some problems popped up due to extended testing coverage and they are fixed as well. Please see individual patches for details. Kirill /cc @vnmabus, @levin.zimmermann /reviewed-by @jerome /reviewed-on !29
Showing
This diff is collapsed.
zodbtools/test/py2py3-venv
0 → 100755
File deleted
File deleted
File added
File added
File added
This diff is collapsed.
File added
File added
No preview for this file type
This diff is collapsed.
File added
File added
File added
This diff is collapsed.
File added
File added
File added
This diff is collapsed.
File deleted
File deleted
File added
File added
File added
This diff is collapsed.
File added
File added
No preview for this file type
This diff is collapsed.
File added
File added
File added
This diff is collapsed.
File added
File added
File added
This diff is collapsed.
-
mentioned in commit kirr/neo@b53e8902
-
mentioned in commit kirr/neo@4e42fef9
-
mentioned in commit kirr/neo@c5b27ee8
-
mentioned in commit kirr/neo@85db9c4f
-
mentioned in commit kirr/neo@952959aa
-
mentioned in commit kirr/neo@80958131
-
mentioned in commit kirr/neo@62ce629f
-
mentioned in commit kirr/neo@06534cb4
-
mentioned in commit kirr/neo@c9cb00cc
-
mentioned in commit kirr/neo@ede4b3bb
-
mentioned in commit kirr/neo@ed2b96ca
-
mentioned in commit kirr/neo@6841930a
-
mentioned in commit kirr/wendelin.core@76f7e270
Please register or sign in to comment