Can't import pysipp after install

[RichParker734]

I just installed pysipp for the first time on windows 10 (Python2.7) using:
pip install git+git://github.com/SIPp/pysipp.git
And after it installed, I tried your example script and got an error. Basically opening a python prompt and typing "import pysipp" generates the following error:

C:\pyfiles>python
Python 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015, 20:32:19) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import pysipp
Traceback (most recent call last):
File "", line 1, in
File "C:\Python27\lib\site-packages\pysipp_init_.py", line 23, in
from . import launch, report, plugin, netplug, agent
File "C:\Python27\lib\site-packages\pysipp\launch.py", line 24, in
class PopenRunner(object):
File "C:\Python27\lib\site-packages\pysipp\launch.py", line 35, in PopenRunner
poller=select.epoll,
AttributeError: 'module' object has no attribute 'epoll'

Any ideas how to fix this?
Thanks!

[vodik]

Hey, so the problem here is that epoll is a Linux subsystem: https://docs.python.org/3/library/select.html#select.epoll

I'd be more then happy to support Windows/OSX if we got some patches for it. In the meanwhile, this is effectively a duplicate of #17.

[goodboy]

@vodik hmm too bad @RichParker734 isn't on py3 because then we should be able to just delegate to selectors..

[goodboy]

@vodik @wdoekes actually what do you two think about cutting py2.7 support?
We could do a first release to pypi, it being the last that supports py2.7 and then we can move all the proc launching mechanics to selectors?

[vodik]

No contest to the idea. Don't have skin in the game.

I'm maintaining two projects that are using pysipp/sipp, but haven't moved them to newer versions of either sipp or pysipp and they can continue on as they are.

I've largely moved on to aiosip as a pysipp replacement.

[wdoekes]

Fine with me. I use pysipp in only one instance and there I probably already use py3.