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

Python 3 compatibility #24

Open
wants to merge 1 commit into
base: develop
from

Conversation

Projects
None yet
4 participants
@jameshilliard

jameshilliard commented Oct 28, 2017

This should get pynetsnmp running under python 3, this shouldn't have any python 2 regressions.

@jplouis

This comment has been minimized.

Show comment
Hide comment
@jplouis

jplouis Oct 28, 2017

Member

Jenkins cannot run this build automatically. Can one of the admins verify this patch? To kick off the pull verification add a comment with "ok to test".

Member

jplouis commented Oct 28, 2017

Jenkins cannot run this build automatically. Can one of the admins verify this patch? To kick off the pull verification add a comment with "ok to test".

@lunkwill42

This comment has been minimized.

Show comment
Hide comment
@lunkwill42

lunkwill42 Oct 30, 2017

There are now three forks dealing with the issue of Python 3 compatibility (and a few other things), one from @kalombos, this one, and my own - but no feedback from @zenoss .

There is clearly an interest in having pynetsnmp work on Python 3. What can be done to get these changes merged and accepted into upstream? Or do we need to fork the entire library properly?

lunkwill42 commented Oct 30, 2017

There are now three forks dealing with the issue of Python 3 compatibility (and a few other things), one from @kalombos, this one, and my own - but no feedback from @zenoss .

There is clearly an interest in having pynetsnmp work on Python 3. What can be done to get these changes merged and accepted into upstream? Or do we need to fork the entire library properly?

@jameshilliard

This comment has been minimized.

Show comment
Hide comment
@jameshilliard

jameshilliard Oct 30, 2017

Maybe it would be a good idea to try and upstream to the twisted project, although it would probably need to be re-licensed/dual licensed.

jameshilliard commented Oct 30, 2017

Maybe it would be a good idea to try and upstream to the twisted project, although it would probably need to be re-licensed/dual licensed.

@lunkwill42

This comment has been minimized.

Show comment
Hide comment
@lunkwill42

lunkwill42 Oct 30, 2017

Relicensing would still require some sort of feedback from @zenoss - which they haven't been very forthcoming with here on GitHub. I don't know anything about the inner workings of the ZenOSS project, my only interest is in the pynetsnmp library itself. Do you or @kalombos know anything about ZenOSS at all, or do we all just share an interest in pynetsnmp?

lunkwill42 commented Oct 30, 2017

Relicensing would still require some sort of feedback from @zenoss - which they haven't been very forthcoming with here on GitHub. I don't know anything about the inner workings of the ZenOSS project, my only interest is in the pynetsnmp library itself. Do you or @kalombos know anything about ZenOSS at all, or do we all just share an interest in pynetsnmp?

@kalombos

This comment has been minimized.

Show comment
Hide comment
@kalombos

kalombos Oct 30, 2017

I forked the library and upload it on pypi. Welcome to contribute.

kalombos commented Oct 30, 2017

I forked the library and upload it on pypi. Welcome to contribute.

@lunkwill42

This comment has been minimized.

Show comment
Hide comment
@lunkwill42

lunkwill42 Oct 30, 2017

I might just take you up on that offer, @kalombos. One fork is better than three. Your original PR #10 towards the @zenoss is still open, though, and keeps updating with every commit to your repo (I think that's why I keep getting notifications about your changes)

lunkwill42 commented Oct 30, 2017

I might just take you up on that offer, @kalombos. One fork is better than three. Your original PR #10 towards the @zenoss is still open, though, and keeps updating with every commit to your repo (I think that's why I keep getting notifications about your changes)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment