Skip to content
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

PR: Fix for access violation error #109

Merged
merged 1 commit into from
Jun 6, 2018
Merged

Conversation

axil
Copy link

@axil axil commented Jun 6, 2018

Fixes #108.

@ccordoba12 ccordoba12 changed the title fix for #108 PR: Fix for access violation error Jun 6, 2018
@ccordoba12 ccordoba12 added this to the v0.5.4 milestone Jun 6, 2018
@ccordoba12
Copy link
Contributor

Thanks a lot for this @axil! Are you able to start terminals in the Jupyter notebook with this change?

@axil
Copy link
Author

axil commented Jun 6, 2018

Not sure what you mean by terminals in Jupyter. As for ipython kernels - yes, it starts them. But it did so without the patch as well.

In the previous issue #59 with the similar symptoms they had troubles with terminal in spyder. I didn't check it out yet. Is it what you're asking about?

I'm on Windows 7 64bit btw.

@blink1073
Copy link
Collaborator

I can confirm this change allows me to launch terminals from Jupyter on Windows 7, thanks @axil!

@ccordoba12
Copy link
Contributor

Thanks @blink1073 for helping us to test that!

@ccordoba12 ccordoba12 merged commit 0f294e7 into andfoy:master Jun 6, 2018
@axil
Copy link
Author

axil commented Jun 7, 2018

Oh, ok. Got it. Looks like a new feature on Windows. Yes, works for me, too.

@wsvma
Copy link

wsvma commented Jun 7, 2018

Thanks for the fix! Sorry for a newbie question. I installed pywinpty via pip. When does a fix like this typically gets propagated so that the fix can be picked up via pip --upgrade?

@wsvma
Copy link

wsvma commented Jun 7, 2018

Nevermind my question. I figured it's just whenever next release (0.5.4) is made.

@axil
Copy link
Author

axil commented Jun 7, 2018

@wsvma I see the following variants:

  1. You can update the file manually, it works, but sort of considered bad practice. That's what I would do if I were you.
  2. The developers can create a pre-release ending with something like "dev" to be installed with pip install --pre
  3. You can wait for 0.5.4.

@ccordoba12
Copy link
Contributor

We'll have other of couple simple issues to solve, then we'll release 0.5.4 (next week at most).

@wsvma
Copy link

wsvma commented Jun 7, 2018

Thanks @axil @ccordoba12

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

Successfully merging this pull request may close these issues.

4 participants