GHC 2017-03-25

9 comments.

, https://git.io/vSIT2 in jarun/googler
> so I can't say when the support will come to CPython's browser module, which is what we use.

By the way, if you're concerned, you should probably search for this issue on https://bugs.python.org/, and create one if it isn't reported already.

, https://git.io/vSITa in jarun/googler
> i guess that is still not possible in the current stable update of win 10 , not sure

It's not possible at the moment, because currently the Linux subsystem can't launch or talk to Win32 processes. I heard the bridge is coming in the Creators Update; in a fairly recent Microsoft demo they were able to launch nodepad++ from the Linux subsystem (don't want to look for the link now) and also talked about how VS talks to gcc and gdb on the Linux subsystem to directly build and debug ELF binaries for Linux. Anyway, I don't use Windows (except for specific gaming purposes...) and only follow Windows development very loosely, so I can't say when the support will come to CPython's `browser` module, which is what we use.

For now you should probably just install Python 3 on the Windows side and run googler there.

I'm closing this issue as solved.

, https://git.io/vSkxK in jarun/googler
#180. Please test if you wish.

, https://git.io/vSkx6 in jarun/googler
Proceed when socket.setsockopt fails
====================================

According to user report (#179), Windows 10's Linux subsystem claims to be Linux but doesn't seem to support the socket options here.

, https://git.io/vSkxi in jarun/googler
That's guarded by a `sys.platform.startswith('linux')` conditional. I guess you're using Windows' Linux subsystem? Apparently they're not all the way there yet. I guess we can ignore errors from `setsockopt`.

> python version 2.7

googler doesn't work with Python 2.7. README:

> googler requires Python 3.3 or later. 

, https://git.io/vSkbi in jarun/googler
You've been given an issue template: https://github.com/jarun/googler/blob/master/.github/ISSUE_TEMPLATE.md. Please don't ignore it.

, https://git.io/vSkbP in Homebrew/homebrew-core
imagemagick@6 6.9.8-3
=====================

Created with `brew bump-formula-pr`.

---

Please remember to
```
brew mirror imagemagick@6
```
when merging.

, https://git.io/vSkbX in Homebrew/homebrew-core
imagemagick 7.0.5-4
===================

Created with `brew bump-formula-pr`.

---

Please remember to
```
brew mirror imagemagick
```
when merging.

, https://git.io/vSkog in gorhill/uMatrix
It's been this way for ages IIRC and happens for my other extensions too. A link to the Chromium bug report has already been posted above: 
https://bugs.chromium.org/p/chromium/issues/detail?id=428044. I doubt anything can be done here.