-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Rewrite the pyOpenSSL implementation in terms of the cryptography one #70
Conversation
98e3389
to
459c39e
Compare
Hmm, I don't understand how this could impact the coverage tests? Motivation here is to clean up usage of deprecated pyOpenSSL APIs that we'd like to remove. |
it looks like I haven't fixed the coverage step after one of many GHA compat breaks. let me look real quick |
thanks! |
ah beautiful! and, if I may say so: pretty cool to have tests in situations like this. |
@hynek do you have a plan for when the next service-identity release will be? Would like to get people off the deprecated APIs. |
I had none, but I can refresh the project (uv ci, metadata, drop old pythons, …) and push a no-other-changes one. |
speaking of, there's nothing that could move #20 along, right? |
Left a comment with a minor status update there.
…On Fri, Oct 25, 2024 at 9:10 AM Hynek Schlawack ***@***.***> wrote:
speaking of, there's nothing that could move #20
<#20> along, right?
—
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAGBBRNYRP77LQLIS7PVTZ5I7KTAVCNFSM6AAAAABQTGCSPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZXG4ZTQNRWG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
All that is necessary for evil to succeed is for good people to do nothing.
|
And re: refreshes/release, that'd be awesome, thanks! |
No description provided.