-
Notifications
You must be signed in to change notification settings - Fork 70
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
New release #219
Comments
We will do some internal discussion around this in the next day or so. You mentioned that you are maintaining a fork of pyeapi. I am curious if whatever changes/updates you have in your fork are already included in the develop branch of pyeapi? |
… On February 1, 2022 11:45:52 PM GMT+01:00, mharista ***@***.***> wrote:
Hi @DavidVentura
We will do some internal discussion around this in the next day or so. You mentioned that you are maintaining a fork of pyeapi. I am curious if whatever changes/updates you have in your fork are already included in the develop branch of pyeapi?
--
Reply to this email directly or view it on GitHub:
#219 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Re-upping this...I need some of the PY3.10 support features for NAPALM so it would be nice to have a new release. |
I'm working towards a new release, but due to switching from python2 to python3 here at arista, many of unit/system tests require update - it’s quite a bit of work. |
@dlyssenko No worries...I actually just realized I can work around the SSL PY3.10 issue entirely inside of NAPALM so it definitely became less pressing. |
@ktbyers ktbyers could you share what SSL issue? I recently merged a PR where I allowed passing SSL context to the pyeapi now. Is that the one, or you meant something else? |
@dlyssenko The PY3.10 SSL handshake issue (due to tighter security defaults i.e. the same one you referenced above for the SSL context). But as I mentioned above, we can work around it in NAPALM without any fix in pyeapi...so I am much less concerned about a pyeapi release. |
closing this one: the submitter found an acceptable w/a, plus the works towards the new release are underway. |
Hi
Is anything blocking a new release? I'm interested in not maintaining my fork anymore -- if there's a pending task or so that you need help with to get a release out, I can help you!
The text was updated successfully, but these errors were encountered: