The Zope/Python Users Group of DC will meet tonight at 7:00PM EDT in Arlington, VA at The Nature Conservancy. If you live in the area, please join us!
Meeting details are here: http://zpugdc.org/meetings/mtg70
In addition we are hosting the monthly Python Programmers Meetup at the same time/location: http://www.meetup.com/zpugdc/calendar/9095442/. So, you get two meetings for the price of one!
If you have any questions, please don't hesitate to contact us:
Alex Clark - aclark at aclark dot net
Matt Bowen - mrbowen at gmail dot com
Hope to see you there.
Alex Clark · http://aclark.net
P.S. We don't have a scheduled speaker at the moment, so the meeting will consist of an around-the-room discussion of your current favorite Python-related technology (e.g. pyjamas, PIL, etc.), followed by a trip to the bar (Rio Grande).
Tuesday, December 2, 2008
Sunday, November 9, 2008
pyCologne Python User Group, Cologne, Germany, November, 12th, Announcement
The next meeting of pyCologne will take place
Wednesday, November, 12th
starting about 6.30 pm - 6.45 pm
at Room 0.14, Benutzerrechenzentrum (RRZK-B)
University of Cologne, Berrenrather Str. 136, 50937 Köln, Germany
Agenda:
Further information including directions how to get to the location can be found at:
http://www.pycologne.de (Sorry, this page is in German only)
starting about 6.30 pm - 6.45 pm
at Room 0.14, Benutzerrechenzentrum (RRZK-B)
University of Cologne, Berrenrather Str. 136, 50937 Köln, Germany
Agenda:
- The GUI-Toolkit pyGTK (Andi Albrecht)
- Network- and Server-Programming with Python (Klaus Bremer)
- Discussion about our this year's christmas party :-)
Further information including directions how to get to the location can be found at:
http://www.pycologne.de (Sorry, this page is in German only)
Tuesday, October 7, 2008
pyCologne Python User Group, Cologne, Germany, October, 8th, Announcement
The next meeting of pyCologne will take place
Wednesday, October, 8th
starting about 6.30 pm - 6.45 pm
at Room 0.14, Benutzerrechenzentrum (RRZK-B)
University of Cologne, Berrenrather Str. 136, 50937 Köln, Germany
Agenda:
Further information including directions how to get to the location can be found at:
http://www.pycologne.de (Sorry, this page is in German only)
starting about 6.30 pm - 6.45 pm
at Room 0.14, Benutzerrechenzentrum (RRZK-B)
University of Cologne, Berrenrather Str. 136, 50937 Köln, Germany
Agenda:
- Introduction into wxPython (Rebecca Breu)
- Examples for Applications of wxPython:
- Vocabulary-Trainer (Ralf Schönian)
- Sudoku (user defined cell-renderer for the Grid-Widget) (Rebecca Breu)
Further information including directions how to get to the location can be found at:
http://www.pycologne.de (Sorry, this page is in German only)
Tuesday, September 9, 2008
pyCologne Python User Group, Cologne, Germany, September, 10th, Announcement
The next meeting of pyCologne will take place
Wednesday, September, 10th
starting about 6.30 pm - 6.45 pm
at Room 0.14, Benutzerrechenzentrum (RRZK-B)
University of Cologne, Berrenrather Str. 136, 50937 Köln, Germany
Agenda:
Further information including directions how to get to the location can be found at:
http://www.pycologne.de (Sorry, this page is in German only)
starting about 6.30 pm - 6.45 pm
at Room 0.14, Benutzerrechenzentrum (RRZK-B)
University of Cologne, Berrenrather Str. 136, 50937 Köln, Germany
Agenda:
- Discussion of the idea to create a pyCologne-Yearbook (2007/) 2008 containing all the events and talks.
- Python 3.0 (3000) Workshop with debate about changes and new features of the Python-Programming-Language e.g.: Strings. Everyone is invited to participate and to provide a little introduction into a Python 3000-Topic.
Further information including directions how to get to the location can be found at:
http://www.pycologne.de (Sorry, this page is in German only)
Monday, August 25, 2008
pyCologne Python User Group, Cologne, Germany, August 13th Notes
The Python User Group in Cologne met at the computer centre of the University of Cologne. The meeting was attended by 16 people. German speakers might want to refer to our wiki page: http://www.pycologne.de.
This time we had as a special guest Guy Kloss, who introduced the New Zealand Python User Group (NZPUG)
and held his talk about Python/C++-Integration:
Thinking Hybrid - Python/C++ Integration (Guy Kloss)
Links
The following Web-Pages were presented during the meeting:
The next meeting will be held on, Wednesday, September, 10th.
Like usual we enjoyed the rest of the evening in our usual italian restaurant having food, drinks and friendly conversation.
This time we had as a special guest Guy Kloss, who introduced the New Zealand Python User Group (NZPUG)
and held his talk about Python/C++-Integration:
Thinking Hybrid - Python/C++ Integration (Guy Kloss)
- The slides can be found at SlideShare: Thinking Hybrid - Python/C++ Integration
- Source-Code and Examples:
- Examples: PyNativeIntegration-examples.tar.gz
- NaSt2D (2D Fluid-Dynamics-Solver): PyNativeIntegration-nast2d.tar.gz
- (on the Web: ftp://ftp.lrz-muenchen.de/pub/science/fluiddynamics/cfd/NaSt2D or http://people.scs.fsu.edu/~burkardt/cpp_src/nast2d/nast2d.html or Version 2.0: http://home.arcor.de/drklaus.bauerfeind/nast/eNaSt2D.html)
EuroPython 2008 from 7th to 12th July 2008 in Vilnius.
Talks from pyCologne-Members: Reimar Bauer (MoinMoin und Mercurial), Stefan Pielicke (SVNChecker), Andreas Schreiber (DataFinder)
Talk by Travis Oliphant (ENTHOUGHT) on 24th of July 2008 at DLR about NumPy, SciPy and the Enthought Tool Suite. The slides and Video can be found at https://wiki.sistec.dlr.de/TechTalks/20080724OliphantNumPy
Talk by Guy Kloss on 13th of August.at DLR about Multithreading vs. Multiprocessing. The slides and Video can be found at https://wiki.sistec.dlr.de/TechTalks/20080813KlossMultithreadingVsMultiprocessing
FrOSCon on 23th/24th of August 2008 at FH Bonn-Rhein-Sieg in St. Augustin Talks/Events from pyCologne-Members: Stefan Pielicke about SVNChecker and "A Python Coffee/Tea-Party" featuring a general introduction into Python and a talk about Turtle-Graphics by Dirk Hünniger and Günter Jantzen.
PyCon UK from 12th to 14th September in Birmingham
Talks by pyCologne-Members: Andreas Schreiber about Organizing the Data Chaos of Scientists
"wxPython in Action" (Noel Rappin, Robin Dunn)
"Python für Kids" (Gregor Lingl) - Introduction to Python for children
- "Turtle Geometry" (Harold Abelson, Andrea diSessa) - A book diving into the mathematics of Turtle-Graphics
Links
The following Web-Pages were presented during the meeting:
The next meeting will be held on, Wednesday, September, 10th.
Like usual we enjoyed the rest of the evening in our usual italian restaurant having food, drinks and friendly conversation.
Wednesday, August 6, 2008
pyCologne Python User Group, Cologne, Germany, August, 13th, Announcement
The next meeting of pyCologne will take place
Wednesday, August, 13th
starting about 6.30 pm - 6.45 pm
at Room 0.14, Benutzerrechenzentrum (RRZK-B)
University of Cologne, Berrenrather Str. 136, 50937 Köln, Germany
Agenda:
Further information including directions how to get to the location can be found at:
http://www.pycologne.de (Sorry, this page is in German only)
starting about 6.30 pm - 6.45 pm
at Room 0.14, Benutzerrechenzentrum (RRZK-B)
University of Cologne, Berrenrather Str. 136, 50937 Köln, Germany
Agenda:
- Discussion of the idea to create a pyCologne-Yearbook (2007/) 2008 containing all the events and talks.
- Python 3.0 (3000) Workshop with debate concerning changes and new features within the Python-Programming-Language e.g. Strings.
Further information including directions how to get to the location can be found at:
http://www.pycologne.de (Sorry, this page is in German only)
Thursday, July 31, 2008
DFW Pythoneers, 4th Sat July, Topics Covered
For the 4th Saturday meeting of July, we had a good group show up for the beginners session at 1pm. The target audience were existing programmers new to Python. We had 10 people besides myself there and then at the regular 2pm start time, some people left and some came in, raising it to 12 people. I presented on the underlying concepts of Python that make it easy to learn yet powerful.
We covered introspection at the Python prompt, using dir(), type(), id() and help() to examine your environment as well as the useful "python -v" and "python -i" arguments. Then we got into names and values and how they are organized into namespaces everywhere you turn in Python. We got into the differences between 'is' and '==', mutability, shared vs non-shared structures and whether names are by-ref or by-value. I went over the simple values then the compound values like mappings, sequences and sets.
Around 2pm when the main meeting began we went over how a Python source file is structured, how it gets converted into multiple codeblocks, which are executed immediately and which are executed later. This was a tricky concept for some with lots of discussion. We covered how the Python module system is derived from that for Modula-3, the various kinds of import statements, the true meaning of the global statement (i.e. not really global overall), how modules are aggregated into a navigable top-level set of in-memory namespaces and some of the metadata you can find in them, like __name__ and __file__.
We took a look at the most common modules all programmers should know, such as __builtins__, sys, os, os.path, string and re (derived from Perl), and a bit on the types module. We reviewed the various control structures that Python gives us and also the ones it lacks, such as switch/case and do/while. We looked at the exception model of Python, how it differs from other languages in its continuability and restartability and the correct usage of exceptions in Python for error conditions, not normal control flows.
We touched lightly on the underlying behavior protocols of Python, for object, number, sequence, mapping, iterator and buffer, how Python uses protocols instead of class derivation for grouping behavior. We then got into Python's idea of OOP, the topmost object class, initializers/destructors and the binding of self and what it means when you have an unbound method. We sidestepped metaclasses and the type hierarchy for now but got in a mention of ducks (type peeking), turtles (all the way down) and monkeys (patching).
And because it is such a key concept, we went over 'callables', how different things can be called transparently and the powerful argument passing mechanism Python uses re positional, keyword and default. We touched a bit on what it means to be iterable and moved on to the more concrete ideas of being subscriptable, from/upto, negative ordinals and subscript ranges or slicing. The third slice argument for skipping, forward and backward, was a popular topic.
It was almost 5pm by then and we were running out of time, so we briefly covered predicates; if a == b, if a is b, if a/not a, and the has_key (in) and hasattr tests. We wrapped up with a couple of short code walkthroughs just to see the concepts in use.
----
This kind of presentation was an experiment to see if there is a demand in our group for a return to the basics of the Python code instead of covering the web framework flavor of the week. Based on this first response, it seemed popular so we'll do it some more at future meetings. I'm going to try to break it apart into relatively standalone topic chapters and, when I do, make those materials available online.
I'll be at WorldCon during our 2nd Sat meeting of August but we'll do this again for the 4th Sat meeting.
We covered introspection at the Python prompt, using dir(), type(), id() and help() to examine your environment as well as the useful "python -v" and "python -i" arguments. Then we got into names and values and how they are organized into namespaces everywhere you turn in Python. We got into the differences between 'is' and '==', mutability, shared vs non-shared structures and whether names are by-ref or by-value. I went over the simple values then the compound values like mappings, sequences and sets.
Around 2pm when the main meeting began we went over how a Python source file is structured, how it gets converted into multiple codeblocks, which are executed immediately and which are executed later. This was a tricky concept for some with lots of discussion. We covered how the Python module system is derived from that for Modula-3, the various kinds of import statements, the true meaning of the global statement (i.e. not really global overall), how modules are aggregated into a navigable top-level set of in-memory namespaces and some of the metadata you can find in them, like __name__ and __file__.
We took a look at the most common modules all programmers should know, such as __builtins__, sys, os, os.path, string and re (derived from Perl), and a bit on the types module. We reviewed the various control structures that Python gives us and also the ones it lacks, such as switch/case and do/while. We looked at the exception model of Python, how it differs from other languages in its continuability and restartability and the correct usage of exceptions in Python for error conditions, not normal control flows.
We touched lightly on the underlying behavior protocols of Python, for object, number, sequence, mapping, iterator and buffer, how Python uses protocols instead of class derivation for grouping behavior. We then got into Python's idea of OOP, the topmost object class, initializers/destructors and the binding of self and what it means when you have an unbound method. We sidestepped metaclasses and the type hierarchy for now but got in a mention of ducks (type peeking), turtles (all the way down) and monkeys (patching).
And because it is such a key concept, we went over 'callables', how different things can be called transparently and the powerful argument passing mechanism Python uses re positional, keyword and default. We touched a bit on what it means to be iterable and moved on to the more concrete ideas of being subscriptable, from/upto, negative ordinals and subscript ranges or slicing. The third slice argument for skipping, forward and backward, was a popular topic.
It was almost 5pm by then and we were running out of time, so we briefly covered predicates; if a == b, if a is b, if a/not a, and the has_key (in) and hasattr tests. We wrapped up with a couple of short code walkthroughs just to see the concepts in use.
----
This kind of presentation was an experiment to see if there is a demand in our group for a return to the basics of the Python code instead of covering the web framework flavor of the week. Based on this first response, it seemed popular so we'll do it some more at future meetings. I'm going to try to break it apart into relatively standalone topic chapters and, when I do, make those materials available online.
I'll be at WorldCon during our 2nd Sat meeting of August but we'll do this again for the 4th Sat meeting.
Subscribe to:
Posts (Atom)
