pip installable/setup.py? about statuspage

[jayfk]

Is this a matter of preference, available time, interest, something else and/or combinations of the aforementioned?

I've found that non python devs have a hard time figuring out what pip is and why it's a good idea to create a virtualenv prior to installing packages.

My goal is to make it super easy to use, so I've decided to ship it as a binary.

I would've probably made a pip installable package, but one of the dependencies (pygithub) has no release on pypi that supports the file api. The package needs to be pulled from github, but I could'nt find a way to tell setup.py to use it.

[jakirkham]

At this point, I'm able to build the binary from source. So, am happy to continue doing it that way personally. Though I figured I'd provide some thoughts on these points.

I can't really provide any suggestions for the first point. Maybe some details or links in the Readme?

As for the last point, that should be doable at least according to this SO answer, but it does feel a bit suboptimal. I suppose vendoring it might be an option. Though some people are opposed to the latter, I think it fits well for your particular use case. Honestly I'd rather see that PR accepted at this point and am not really sure why it hasn't happened yet.

In any event, none of this stops one from still shipping binaries. It just provides another way of getting at a release that is more familiar to the average Python user.

[jayfk]

There's now a pip-installable package of statuspage available, see b8c2f71