Skip to content
This repository has been archived by the owner on Sep 27, 2021. It is now read-only.

Clarify maintenance status #62

Open
djc opened this issue Sep 27, 2021 · 3 comments
Open

Clarify maintenance status #62

djc opened this issue Sep 27, 2021 · 3 comments

Comments

@djc
Copy link
Member

djc commented Sep 27, 2021

I'm no longer motivated to maintain nnpy, and I don't know anyone else who is. Would be good to clarify the maintenance status in the README and/or archive the repo to make this clear to (potential) users. @gdamore any thoughts?

@Ahmadreza-Shahrokhshahi FYI.

@gdamore
Copy link

gdamore commented Sep 27, 2021

maybe we can add a comment to the table where nanomsg implementations are listed.

can I ask if there is a reason for your change of heart?

@gdamore
Copy link

gdamore commented Sep 27, 2021

actually as this is just for nanomsg (legacy) you should probably just archive the project. You can add a reference to pynng which is more actively maintained and is built against NNG.

@djc
Copy link
Member Author

djc commented Sep 27, 2021

can I ask if there is a reason for your change of heart?

It's been five years since I originally wrote the code as a sort of proof of concept, because I thought nanomsg was cool. For myself, I never ended up actually using nanomsg for anything interesting, and on top of that I've mostly stopped writing Python code in favor of writing Rust code. So if I would start using nanomsg/nng again I would probably still not be interested in using this library.

I'll add a note about pynng to the README and archive the repo.

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

No branches or pull requests

2 participants