I'm happy to invite you to a Twisted sprint on Saturday, November 1st
in Cambridge, Massachusetts. ClusterHQ will be hosting up to twenty
(20) Twisted sprinters at the Cambridge Innovation Center ("Coronet
City" room) in Kendall Square from 10AM until 11PM. The sprint topics
are attendee choice - hacking on any part of Twisted is welcome. A
large part of the ClusterHQ team will be taking part in the sprint.
ClusterHQ is developing Flocker, a data management tool for use with
Docker written in Python and based on Twisted. Follow us on Github:
ClusterHQ will provide lunch and dinner (something like delivery
pizza, comment on the meetup page if you'd like to suggest
Find details and chat about sprint topics at the Boston Twisted Python
Early birds, feel free to contact me off-list about meeting up for
around 9AM before the sprint starts.
Space at CIC is limited. Please RSVP on the Meetup page!
See you there,
I have a couple projects I am working on where I would like to make HTTPS
requests using Twisted. I reviewed the articles "Using TLS in Twisted" 
and "Using the Twisted Web Client" (section "HTTP over SSL") . It seems
like various options exist that will allow me to make HTTPS requests using
the CA certs bundled on the client OS.
I would like to be able to tell my HTTPS clients to accept specific
*internal* CA certificates *in addition* to the certificates provided by
the OS. Initially, I thought this might be possible by passing a custom
t.w.c.BrowserLikePolicyForHTTPS to the t.w.c.Agent as its `contextFactory`
argument. I wasn't quite sure how to go about doing this, so I got some
advice on StackOverflow . With some slight modifications to the solution
presented there, I was able to create a custom Trust Root that accepted a
list of paths to CA cert files in PEM format that I wanted to add to the
client. The custom trust root is passed to the BrowserLikePolicyForHTTPS.
The policy is passed to the Agent.
The one hitch is that the IOpenSSLTrustRoot interface upon which my custom
trust root is based is located in `twisted.internet._sslverify`, which
if I understand correctly, is a private module and not supposed to be used
as an API. Is there a *supported* way to specify *additional* CA certs to
use during SSL verification when making HTTPS requests using Twisted? If
so, what is the recommended method?
Another related concept that was not clear to me is how one might specify
the SSL method (e.g. SSLv23_METHOD, SSLv3_METHOD, etc.) when making the
request. Is there some recommended way to pass options to indicate the SSL
method that ought to be used?
Any guidance would be appreciated.
On 7/1/13 1:00 PM,Phil Mayers <p.mayers(a)imperial.ac.uk> wrote:
> > I'm a newbie to Python, but not programming. However, my problem is
> > replacing an antiquated web-based classroom-attendance oriented
> > software app.
If you are looking at python, you have a lot of choices.
The first choice is which database to use, object-oriented, or relational.
If you choose relational, then django is the mainstream choice.
If you choose object oriented, then you can consider ZODB. It stores a
persistent network of objects. Which leads to either the Zope 3 /
ZTFY.org web framework, or else
pyramid. Pyramid is good for simpler applications, as they get more
complicated, I would recommend ztfy.org. and wiki.ztfy.org
Better yet, just get a complete school application at
built on top of zope 3, very easy to make any customizations you want,
that is the greatest strength of Zope 3.