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

New release #219

Closed
DavidVentura opened this issue Feb 1, 2022 · 8 comments
Closed

New release #219

DavidVentura opened this issue Feb 1, 2022 · 8 comments

Comments

@DavidVentura
Copy link
Contributor

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!

@mharista
Copy link
Contributor

mharista commented Feb 1, 2022

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?

@DavidVentura
Copy link
Contributor Author

DavidVentura commented Feb 1, 2022 via email

@ktbyers
Copy link

ktbyers commented Sep 1, 2022

Re-upping this...I need some of the PY3.10 support features for NAPALM so it would be nice to have a new release.

@dlyssenko
Copy link
Contributor

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.

@ktbyers
Copy link

ktbyers commented Sep 1, 2022

@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.

@dlyssenko
Copy link
Contributor

@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?

@ktbyers
Copy link

ktbyers commented Sep 1, 2022

@dlyssenko The PY3.10 SSL handshake issue (due to tighter security defaults i.e. the same one you referenced above for the SSL context).

napalm-automation/napalm#1731

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.

@dlyssenko
Copy link
Contributor

closing this one: the submitter found an acceptable w/a, plus the works towards the new release are underway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants