Closed dmitry-a-morozov closed 10 years ago
What's a plan regarding this issue? Do we want to fork http://github.com/pythonnet/pythonnet/ soon or we'll give those guys some time to settle down? Our expectations should be minimal.
I'd recommend you fork (for bug fixes), simultaneously cooperate with those who want to reshape the project (even help them out), and then fold the bug fixes back into any future "settled down" version.
I hope to revive the pythonnet project, but we need help. The migration to github is now done and it is the new official home, but that is only the start. Any help from your side in terms of bug fixes or anything else would be greatly appreciated. The future of the project is nevertheless unclear because I am not sure whether we will have a stable group of maintainers. If you want to help on that front, fantastic!
A fork (https://github.com/fsprojects/pythonnet) has been made to accommodate bug fix. For now we take dependency on our local customized version of Python for .NET.
I open an issue here https://github.com/pythonnet/pythonnet/issues/3 Bottom line for us that we might need to use custom-compiled version for some time. Seems like there is some movement around better Python for .NET support but hard to says at this point when those guys will start maintain the library actively again.