[Chandler-dev] Chandler new-version detection

[Heikki Toivonen]

Morgen Sagen wrote:
> Under the hood it uses urllib, which we can configure to honor whatever
> proxy settings the user has entered in Chandler.  Heikki mentioned a
> desire to use HTTPS which means we would need proxy support for HTTPS as
> well.
> 
> What do people think about using setuptools for new-version detection?

In principle that sounds great; I am not keen on reinventing either.

Would this require putting something on cheeseshop for setuptools to
detect a new Chandler version, or can you tell setuptools where to look?
AFAIK cheeseshop is not available over SSL.

I think making setuptools support secure SSL would be easy (if nothing
else, replacing socket.ssl by M2Crypto's implementation), but not sure
about HTTPS proxy. M2Crypto's httpslib has HTTPS proxy support (patch
written by a 3rd party, I haven't used it myself), so maybe that could
be adapted easily... Of course, I haven't looked at setuptools code at
all so I don't know for sure how any of this would work.

-- 
  Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20071121/f5c55679/signature.pgp