New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.0.0 release date ? #598
Comments
Do you have a process on which we could iterate ? |
@tmmorin: sounds like the plan 😃 |
Yes, but the existing unit test suite does already pass with python3. (the other plan would be: run 2to3, but not to modify the source, which would become non-python2 compatible, but to see all the places that can be changed for python3. But filtering all the suggested changes, to keep only the ones that are strictly needed, is cumbersome...) |
When I ran the code "by hand" it fails so I assume the test suite is broken ... again ... |
In fact, the only test suite I had been running for the initial python3 work was qa/tests/*.py I've now a work branch in my repo which is passing much more tests from qa/bin. |
@tmmorin do you want to share/merge your branch - so I can make sure that any regression in the test suite is fixed in both p2 and p3 please ? |
I had a few more things to merge first, but now here is the branch: some more tests pass with my proposed fix for #613, but not all of them |
the whole test suite (except qa/bin/conversation tests that seem hard to pass in python2 as well) seem to be happy with python3 anything else missing for releasing a 4.0.0beta ? |
I need to change a few things ( version reported for JSON and TEXT interface ), but I should be able to release in the next few days. |
4.0.0 was released ! |
Hello,
The only change holding back the release of ExaBGP 4.0.0 is python3 support (lots was already done by @tmmorin with six).
It seems that the big'gy will be the conversion of all the string used for encoding / decoding into b"" string.
Once this is completed, I am "happy" to release. Help welcomed !
The text was updated successfully, but these errors were encountered: