You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi David. From the archives [https://mail.python.org/pipermail/pythondotnet/2014-February/001472.html] you mentioned:
"My immediate next goal would be to release a stable version. So my sense is that we should not try to do new features, but first get something out that works again."
Is there a rugged definition of "that works again"? Assuming Python for .NET worked in the past, what year would I be in, what OS would I be using, and what versions of Python and .NET would I have installed?
The text was updated successfully, but these errors were encountered:
I am not sure, I only very recently joined this project. I believe things broke for good with the release of .Net 4.5.1 (the version released with Win 8.1). We don't have a fixed timeline for a working release. There are really only two people working on this, and I believe for both of us this is a sideline project.
Hi David. From the archives [https://mail.python.org/pipermail/pythondotnet/2014-February/001472.html] you mentioned:
"My immediate next goal would be to release a stable version. So my sense is that we should not try to do new features, but first get something out that works again."
Is there a rugged definition of "that works again"? Assuming Python for .NET worked in the past, what year would I be in, what OS would I be using, and what versions of Python and .NET would I have installed?
The text was updated successfully, but these errors were encountered: