Skip to content
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

Character vs. byte strings fix #300

Merged
merged 6 commits into from
Feb 16, 2024
Merged

Conversation

tofu-rocketry
Copy link
Member

@tofu-rocketry tofu-rocketry commented Feb 16, 2024

Resolves #146
Resolves #209

Note that this is a conservative fix and does not add Unicode support so that the behaviour matches between Python 2 and 3.

Unicode support is tracked in #299.

Tested manually between Python 2 and 3, sending and receiving for each, and using dirq and directory sending.

RedProkofiev and others added 4 commits February 6, 2024 16:09
We don't (yet) want to test against unicode.
Some compatability issues raised in testing with 3.3.0
- Add decoding when sending messages to fix Python 3 issues.
- Set both to ascii only as this maintains the behaviour with Python 2
  for now while in transition period.
@tofu-rocketry tofu-rocketry added this to the 3.4.0 milestone Feb 16, 2024
@tofu-rocketry tofu-rocketry self-assigned this Feb 16, 2024
@tofu-rocketry tofu-rocketry requested a review from a team as a code owner February 16, 2024 12:25
Copy link
Member

@gregcorbett gregcorbett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't think of a better way forward RE: the docker build than what you propose.

@RedProkofiev
Copy link
Contributor

I'm very confused on the docker stuff, but Greg's suggestion might work? Mainly just here to log that if it's a PyOpenSSL/crypto interaction of versions, we need to have as late a version of Crypto as possible (3.3.2 with py2 compatibility) and PyOpenSSL (21.0.0) :)

- Set pyopenssl >=19.1 so that it is compatable with cryptography
  >=3.3.0
- Revert cryptography requriement to 3.3
Pin to 3.3.2, the latest version that's still compatible with Python 2.
@tofu-rocketry tofu-rocketry merged commit 39a6a22 into apel:dev Feb 16, 2024
9 of 10 checks passed
@tofu-rocketry tofu-rocketry deleted the 146-bytes branch February 16, 2024 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Check issue about type (str/bytes) of messages in outgoing queue bytes vs. text and python 3
3 participants