I’m Planning a PyCon 2010 Talk

During Andrew Kuchlings’s talk on How to Give a Python Talk he mentioned the top rated PyCon talks over the years. I was extremely surprised to see the talk Mike Pirnat and I gave in 2006 on the list. The video for Python Can Survive In The Enterprise is available here if you missed it.

I’m now motivated to do a talk next year. I have a large number of commitments so I’m starting the preparation early.

Possible Topics:

  1. Python Dependency Injection and snake-guice
  2. Virtual Hosting with WSGI - applications on multiple domains in the same app server instance

All feedback is welcome. I’m open to talk suggestions. Is there something that I do or work on that may make an interesting talk?

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • Technorati

Comments

  • @Graham


    Sounds like it yes. I am not familiar with that. This style of virtual hosting is very nice and allows our websites to easily scale.

  • So, effectively doing what the so called virtual host monster in Zope did. That is, handle the virtual hosting within the application itself in same memory space rather than using an external generic mechanism which splits different virtual hosts into different processes.

  • @Graham


    At AGI we have a single application server that is able to host all of our websites at the same time in the same process. Our new approach is to use a series of WSGI pipelines. I was thinking about talking about that setup.

  • When you say 'WSGI', what particular WSGI hosting mechanism are you talking about? Or is the intent to give an overview of the various options available.

  • dave noyes

    Very cool Dave. I hope to be at PyCon 2010 and attend your talk. thumbs up

  • +111 for dependency injection and snake-guice -- and PLEASE accompany that with a concise but powerful coverage of WHY monkey patching is NOT a good alternative if you can avoid it!-)

blog comments powered by Disqus