Mattwmaster58
Mattwmaster58
This library seems to have been abandoned, however I and others have been working on an updated fork — [pyppeteer2](https://github.com/pyppeteer/pyppeteer2). It's up on PyPi and the fix has already been...
We're working to take over the `pyppeteer` name on Github for as seamless as a transition as possible: https://github.com/pypa/pypi-support/issues/344
Hi @apischke, it looks like this project has been abandoned. You may want to consider the active fork [pyppeteer2](https://github.com/pyppeteer/pyppeteer2). Feel free to create an issue there if your problem persists...
duplicate of #62
@mostafamirzaee It's actually not an issue in the websockets library per se, rather in chrome and pyppeteer. Chrome doesn't respond to pings over websockets, making the websockets (rightly) believe Chrome...
Hi @PiAreSquared, it looks like this project has been abandoned. You may want to consider the active fork [pyppeteer2](https://github.com/pyppeteer/pyppeteer2). Feel free to create a PR there if your problem persists...
Hi @wonghang , it looks like this project has been abandoned. You may want to consider the active fork [pyppeteer2](https://github.com/pyppeteer/pyppeteer2). Feel free to create an issue there if your problem...
Hi @abhay-kum , it looks like this project has been abandoned. You may want to consider the active fork [pyppeteer2](https://github.com/pyppeteer/pyppeteer2). Feel free to create an issue there if your problem...
Hi @derlin , it looks like this project has been abandoned. You may want to consider the active fork [pyppeteer2](https://github.com/pyppeteer/pyppeteer2). Your issue will persist with latest version, however, when the...
Hi @ironexmaiden , it looks like this project has been abandoned. You may want to consider the active fork [pyppeteer2](https://github.com/pyppeteer/pyppeteer2). Feel free to create an issue there if your problem...