Change package name to be pywinpty about pywinpty HOT 8 CLOSED

I agree with @ccordoba12, there are more packages that have different package and module names, such as OpenCV:

conda install opencv -c conda-forge

import cv2

from pywinpty.

That's my take too, i.e. use pywinpty. This is also important to disambiguate the original library from its Python bindings, else things become a nightmare.

For example, we have pip install graphviz and conda install graphviz, which do different things (the first one installing the bindings and the second one the library).

from pywinpty.

But as winpty is a C program, I don't see why we would have any module naming ambiguity problems. I think there would be problems if the package was called winpty.

from pywinpty.

@andfoy please change the python package to pywintpty both the name and folder (module name)

from pywinpty.

Ok, I will do the changes. But I still think that is more intuitive to import winpty, as we're wrapping winpty library. For instance, at installation time we would execute:

pip install pywinpty

But to use it we would execute:

import winpty

from pywinpty.

It's the same with pyzmq:

pip install pyzmq

import zmq

so we have a good precedent here ;-)

from pywinpty.

@andfoy

I agree with @ccordoba12, there are more packages that have different package and module names, such as OpenCV:

conda install opencv -c conda-forge
import cv2

Is actually a bad example, cause there is no coherence on that naming.

from pywinpty.

I'm sure cv2 is the C library name. If so, it's the right thing to do :-)

from pywinpty.