Thanks to visit codestin.com
Credit goes to github.com

Skip to content

A Working pythonnet #22

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

Closed
jomido opened this issue Mar 17, 2014 · 1 comment
Closed

A Working pythonnet #22

jomido opened this issue Mar 17, 2014 · 1 comment

Comments

@jomido
Copy link

jomido commented Mar 17, 2014

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?

@davidanthoff
Copy link
Contributor

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.

lostmsu pushed a commit to losttech/pythonnet that referenced this issue Jun 17, 2019
…ovements-dispose-clrobject

Performance improvements ClrObject - Dispose PyObj
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants