I still do not have the time of motivation to maintain this project to the level it requires.
The are a couple of major problems with nanomsg and nanomsg-python
1) Building the module is requires more knowledge of building C projects than I think is reasonable;
2) nanomsg has some unfixed bugs
To solve both of these my plan is to take the nanomsg source code and "vendor" it with the python module so that building the module becomes a lot simpler and it would be easy to build and maintain pip wheels for windows so that no building is required. This would improve things a lot - I also plan to debug the long standing deadlock issues.
I started this work but don't have time to finish it at the moment - I think it will be 3 or 4 months before I find time to look at it again.
We can plod on as is but is anyone want to take over please reply here of message me on twitter @agjasimpson
Following on from https://github.com/tonysimpson/nanomsg-python/issues/43
I still do not have the time of motivation to maintain this project to the level it requires.
The are a couple of major problems with nanomsg and nanomsg-python
1) Building the module is requires more knowledge of building C projects than I think is reasonable; 2) nanomsg has some unfixed bugs
To solve both of these my plan is to take the nanomsg source code and "vendor" it with the python module so that building the module becomes a lot simpler and it would be easy to build and maintain pip wheels for windows so that no building is required. This would improve things a lot - I also plan to debug the long standing deadlock issues.
I started this work but don't have time to finish it at the moment - I think it will be 3 or 4 months before I find time to look at it again.
We can plod on as is but is anyone want to take over please reply here of message me on twitter @agjasimpson
Thank,
Tony