PyWeek 6 will run from 00:00 UTC on March 30th through to 00:00 UTC on April
6th.
Registration is NOT OPEN YET. It will open on Friday 2008/02/29.
If you're new (or even coming back again) please have a look at the rules and
help pages at http://www.pyweek.org/
The PyWeek challenge:
1. Invites entrants to write a game in one week from scratch either as an
individual or in a team,
2. Is intended to be challenging and fun,
3. Will hopefully increase the public body of game tools, code and
expertise,
4. Will let a lot of people actually finish a game, and
5. May inspire new projects (with ready made teams!)
Entries must be developed in Python during the challenge, and must incorporate
some theme decided at the start of the challenge.
--
Visit the PyWeek website:
http://www.pyweek.org/
The O'Reilly Open Source Convention (OSCON) is accepting proposals for
tutorials and presentations. The submission period ends Feb 4.
OSCON 2008 will be in Portland, Oregon July 21-25. For more information
and to submit a proposal, see
http://conferences.oreilly.com/oscon/
--
Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/
"All problems in computer science can be solved by another level of
indirection." --Butler Lampson
===============================
Release of a new ViTables video
===============================
`Carabos <http://www.carabos.com/>`_ is very happy to announce the
second video of the series dedicated to introducing the main features
of ViTables to the public.
http://www.carabos.com/products/videos/vitables-2-queries
`ViTables <http://www.carabos.com/products/vitables>`_ is a GUI for `PyTables
<http://www.pytables.org>`_. It allows to open arbitrarely large PyTables and
HDF5 files and browse their data and metadata in a variety of ways.
This second video explains in depth how to quickly query multi-billion row
tables using ViTables in combination with OPSI [1]_, the powerful indexing
engine that comes with PyTablesPro. The covered topics are:
* how to do queries involving several fields a.k.a complex queries
* how to include the indexes of the selected rows in a query result
* detailed description of the queries dialog
* how indexing fields with OPSI affects the speed of queries
It has a running length of about 8 minutes, so you can watch it during any
short break.
We would like to hear your opinion on the video so we can do it better
the next time. We are also open to suggestions for the topics of
future videos.
.. [1] http://www.carabos.com/docs/OPSI-indexes.pdf
Best regards,
--
::
\ / Vicent Mas http://www.carabos.com
0;0
/ \ Cárabos Coop. Enjoy Data
V V
" "
A "Publicizing PyCon" kit has been posted at the PyCon website.
PyCon has always relied on the community to get the word out. This
year, we've put together a "Publicizing PyCon" page under the "Helping
Out" section of the PyCon website, at
http://us.pycon.org/2008/helping/publicize/
It includes
* Blog badges
* Sample announcement emails
* A poster/flyer to print out
* A slide to drop into live presentations
Now is the perfect time to spread the word - registration is open, and
early-bird rates are available through Feb. 20. Thanks for your help!
--
- Catherine
http://catherinedevlin.blogspot.com/
*** PyCon 2008 * Chicago * March 13-20 * us.pycon.org ***
--
- Catherine
http://catherinedevlin.blogspot.com/
*** PyCon 2008 * Chicago * March 13-20 * us.pycon.org ***
Announcing epydoc 3.0
~~~~~~~~~~~~~~~~~~~~~
Webpage:
http://epydoc.sourceforge.net/
Download:
http://tinyurl.com/yoo6d7
About epydoc
~~~~~~~~~~~~
Epydoc is a tool for generating API documentation for Python modules,
based on their docstrings. A lightweight markup language called
epytext can be used to format docstrings, and to add information about
specific fields, such as parameters and instance variables. Epydoc
also understands docstrings written in reStructuredText, Javadoc, and
plaintext.
Improvements in Version 3.0
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Version 3.0 of epydoc adds support for extracting documentation
information using both introspection (i.e., importing & inspecting the
modules programmatically) and parsing (i.e., reading the source code of
the modules); and for combining both sources of information. This is
important because each source has its own advantages and disadvantages
with respect to the other. See the epydoc FAQ for more information
about the relative benefits of introspection and parsing, and why it's
good to merge information from both sources:
http://epydoc.sourceforge.net/faq.html#introspect_vs_parse
Version 3.0 also adds the following features:
* Support for variable docstrings.
* Automatic generating of source code graphs, including class trees,
package trees, uml class graphs, and import graphs.
* Syntax highlighted source code, including links from identifiers
back into the documentation.
For more details about what's new in Epydoc 3.0, see:
http://epydoc.sourceforge.net/whatsnew.html
<P><A HREF="http://epydoc.sourceforge.net/">epydoc 3.0</A> - a tool
for generating API documentation for Python modules, based on their
docstrings. (29-Jan-08)
----------------------------------------------------------------------
Edward Loper edloper(a)gradient.cis.upenn.edu
http://www.cis.upenn.edu/~edloper/
----------------------------------------------------------------------
Hi All,
Pydev and Pydev Extensions 1.3.12 have been released
Details on Pydev Extensions: http://www.fabioz.com/pydev
Details on Pydev: http://pydev.sf.net
Details on its development: http://pydev.blogspot.com
Release Highlights in Pydev Extensions:
-----------------------------------------------------------------
* Mark occurrences: only requested on mouse-clicks and cursor changes.
* Code-Analysis: No longer running in UI-Thread (bug which slowed
things down in 1.3.10 and 1.3.11).
* Code-Analysis: Cache optimizations.
* Code-Analysis: Fixed 'statement without effect' when raising
exception with arguments without using the exception constructor.
* Code-Analysis: Fixed 'statement without effect' on tuple creation.
* Code-Analysis: __path__ found for packages (__init__.py files).
* Context-insensitive info: Correctly updated when code-analysis is
off (or if file is not analyzed).
Release Highlights in Pydev:
----------------------------------------------
* Code Coverage: coverage.py updated to version 2.78
(http://nedbatchelder.com/code/modules/coverage.html).
* Optimization: Caches (with no memory overhead) added for a number of
situations, which can speed completion requests a lot (up to 40x on
tests).
What is PyDev?
---------------------------
PyDev is a plugin that enables users to use Eclipse for Python and
Jython development -- making Eclipse a first class Python IDE -- It
comes with many goodies such as code completion, syntax highlighting,
syntax analysis, refactor, debug and many others.
Cheers,
--
Fabio Zadrozny
------------------------------------------------------
Software Developer
ESSS - Engineering Simulation and Scientific Software
http://www.esss.com.br
Pydev Extensions
http://www.fabioz.com/pydev
Pydev - Python Development Enviroment for Eclipse
http://pydev.sf.nethttp://pydev.blogspot.com
Hi all,
Versions 1.2 of shm and shm_wrapper -- two modules which enable IPC
(shared memory and sempahores) via Python -- are now available. The
former is Vladimir Marangozov's old shm module with some bug fixes, the
latter is my wrapper which I find more Pythonic.
Changes from version 1.1 include code that should enable shm to be used
in conjunction with threads as well as setup and compilation
improvements for various platforms.
Enjoy!
http://NikitaTheSpider.com/python/shm/
--
Philip
http://NikitaTheSpider.com/
Whole-site HTML validation, link checking and more
As has occurred since the inception of PyCon, there will be a sprint
on the Python core at this year's conference!
If you will be attending PyCon (or will be in Chicago during the dates
of the sprints), attending the sprint is a great way to give back to
Python. Working on Python itself tends to deepens one knowledge of the
language and the standard library. Plus it is just plain fun getting
to sit around some tables with fellow Python programmers for several
days (the sprint will last four days, but you do not need to attend
all four days to participate).
The sprint is open to everyone of all skill levels. We can always use
help with things from updating documentation to preparing for the next
release of Python 3.0.
On Sunday evening of the conference there will not only be a sprint
intro session, but also a tutorial on how to develop for Python.
Details will be covered from where to look in the code base for things
to some best practices tips.
If you are interested enough to want to sign up to attend, please go
to http://wiki.python.org/moin/PyCon2008/SprintSignups/Python and add
your name and email address. If you have questions you may email me.
Please sign up for the sprint by the end of February as an email on
what you need to do beforehand will be sent at that time based on the
sprint sign-up page.
And if you are not attending PyCon, we will most likely have several
people in attendance on IRC, thus allowing even people not at PyCon to
participate!
-Brett Cannon
Python core sprint coach, PyCon 2008
On behalf of the Storm development team, I'm proud to announce that
the release 0.12 is out! This is a very exciting release, as it
brings several fixes and quite a few new features.
Thank you very much to everyone who contributed.
Storm is available at: https://storm.canonical.com
Improvements
------------
- The Connection will reconnect automatically when connection
drops are detected and a rollback is performed. As a result,
the Store should handle reconnections in a seamless way in
most circumstances (#94986, by James Henstridge). This is
supported in the MySQL and PostgreSQL backends.
- Store.flush() will not load values inserted in the database.
Instead, undefined variables are set to AutoReload, and resolved
once first accessed. This won't be noticeable in normal usage,
but will boost the performance of inserts.
- Support in the postgres backend to use the RETURNING extension of
the INSERT statement to retrieve the primary key on inserts for
object identity mapping (PostgreSQL >= 8.2 only)
- Introduced a cache mechanism that keeps the N last retrieved objects
in memory to optimize cases where the same object is retrieved
often while no strong references are kept elsewhere. Implemented by
Bernd Dorn, from Lovely Systems.
- Improved support for TimeDelta properties on all backends. Many
more formats are accepted now, and some issues were fixed.
Bug fixes
---------
- TimeDelta was added to storm.locals.
- Fixed TimeDelta support in SQLite, MySQL, and PostgreSQL,
and enabled base test for all backends to ensure that it
continues to work.
- Schema names are accepted in __storm_table__ when using
PostgreSQL as the database (e.g. "schema.table"). (#146580,
reported by James Mayfield)
- Test runner handles path correctly on Windows, and SQLite
tests won't break (patch by Ali Afshar).
- In the SQLite backend, ensure that we're able to recommit a
transaction after "database is locked" errors. Also make sure
that when this happens the timeout is actually the expected
one (patch by Richard Boulton)
- TransactionFailedError is now imported from the public
place: ZODB.POSException (#129715, by James Henstridge).
- TimeDelta was added to storm.locals.
- Tables named with reserved keywords are properly escaped.
- Reserved keywords on column names are properly escaped when
part of an insert or update statement (#184849, by Thomas Herve).
- Prevent cached objects from issuing selects to retrieve their
data when find()s were previously made and already brough
their data (#174388, reported and fixed by Bernd Dorn).
- Fixed bug which caused an object to be readded to the store
when a reference of an object that had already been removed
was looked up.
- Prevent pathological case which happens when a statement like
"SELECT ... WHERE table.id = currval(...)" is executed in
PostgreSQL. The change is only meaningful on PostgreSQL < 8.2,
as newer versions will use the RETURNING extension instead.
- Specify both of the joining tables explicitly when compiling Proxy,
so that it doesn't break due to incorrect references in the ON clause
when multiple tables are used (reported in #162528 by S3ym0ur and
Hamilton Tran)
- MySQL client charset now defaults to UTF-8 (reported
by Brad Crittenden).
--
Gustavo Niemeyer
http://niemeyer.net
