WHAT IS IT:
The Sybase module provides a Python interface to the Sybase relational
database system. It supports all of the Python Database API, version
2.0 with extensions.
The module is available here:
The module home page is here:
CHANGES SINCE 0.38pre1:
* Add structured error information to Sybase.DatabaseError thanks to
patch provided by Gregory Bond (close tracker 1631902)
* Resurrected Sybase.Bulkcopy functionality thanks to patch provided
by Gregory Bond (close tracker 1632916)
* Corrected AttributeError when locking is off (close tracker 1637942
reported by Jim Nusbaum)
* Corrected incorrect type mx.DateTime.DateTime returned by
Sybase.Date() in "mx" datetime mode. This type is not supported by
* Corrected crash on a BLK object when debug is enabled (close tracker
1630941 reported by Gregory Bond)
* rowcount is now propagated to Cursor (corrects tracker 1621003)
* Added support for python datetime type in DataBuf and as parameter
* Corrected Date, Time and Timestamp functions when using mx.DateTime
or native python datetime types
* Corrected DATETIME as cursor.description still returns native Sybase
* Corrected blk_describe always returns (status, None) thanks to patch
by Phil Porter
* Patch to handle CS_LONG type based on patch by Paul Rensing
MAJOR CHANGES SINCE 0.37:
* This release works with python 2.5
* It also works with sybase 15
* It works with 64bits clients
* It can be configured to return native python datetime objects
* The bug "This routine cannot be called because another command
structure has results pending." which appears in various cases has
* It includes a unitary test suite based on the dbapi2.0 compliance
A week or so ago, the Dallas and Houston Python User Groups met online in a
chat room, to discuss the possibility of a regional Python conference. There
was interest on all sides. Some of the Dallas members had recently attended
their second BarCamp (http://barcamp.org), defined as an ad-hoc gathering born
from the desire for people to share and learn in an open environment.
From this interaction as well as the realization, after the Dallas group
hosted PyCon in 2006 and will again in 2007, that a conference is a *lot* of
work, we decided to try the idea of running an "unconference".
An unconference (http://en.wikipedia.org/wiki/Unconference) is a conference
where the content of the sessions is driven and created by the participants,
generally day-by-day during the course of the event, rather than by a single
organizer, or small group of organizers, in advance.
And tossing around some names, we decided upon "PyCamp". There is much to be
discussed re dates, location and how it will operate, so I set up the website:
and a Mailman instance for mailing lists at:
The rough idea is to hold a Texas-wide unconference, perhaps sometimes in
August and near Austin. There was also the idea of holding a rotating
unconference that moves between Dallas, Austin and Houston, say twice a year.
To minimize the impact on participant (not attendee - this is an
unconference after all where you are expected to get involved) schedules, it
was suggested we hold it over a weekend. We'd meet for dinner/drinks on a
Friday evening, hold our talks at some hotel on Saturday and early Sunday, and
then travel home Sunday evening.
You'll notice that I keep saying "maybe", "suggested" and other weasel words
above. This is because I'm not the conference chair (thankfully) and we're
not imposing the schedule/rules. Ralph Green of Dallas has volunteered to
wrangle the project and website, and is one of those who has attended a
BarCamp. We need the creative energy and participation by members of all
Python User Groups in Texas and invite you to join the Texas PyCamp mailing
list (see above URL).
Oh, and we didn't want to be the only ones having fun, so the PyCamp URL, wiki
and mailing lists are available to other states or regions than Texas.
Hopefully we can start a movement toward regional PyCamp Unconferences
everywhere. If you're unfortunate enough to not live in Texas, drop me an
email and I'll set you up your own regional section of the PyCamp site.
Jump in and let's talk. And with PyCon rapidly approaching, we'd like to meet
face-to-face with kindred spirits there. I'll make sure it gets on the
Python Advocacy Coordinator
Dallas-Ft. Worth Pythoneers Coordinator
PyCon 2007 Co-Chair
Pyrex 0.9.5.1a is now available:
This is a glitch-fix nanorelease to correct a problem
with the setup.py file. The list of packages to install
is now calculate dynamically, so that it will work with
or without the testing files.
What is Pyrex?
Pyrex is a language for writing Python extension modules.
It lets you freely mix operations on Python and C data, with
all Python reference counting and error checking handled
I'm happy to release Paste 1.2. This release contains a mix of small
features and bug fixes. This is only a release of core Paste (not Paste
Script or Deploy), which contains the WSGI tools.
What Is Paste?
Install: easy_install -U Paste
Paste is a set of WSGI components, each of which can be used in
isolation. But mixing them together leads to powerful chemical
reactions which can be harnessed for good.
These components let you do things like create applications that proxy
to other websites, mount multiple applications under different
prefixes, catch exceptions and interactively inspect the environment,
and much more.
Paste Deploy is a configuration system for these components. Paste
Script is a jack of all trades that builds new project file layouts,
runs WSGI server stacks, and does application deployment.
See http://pythonpaste.org/news.html for details
* Backward incompatible change in paste.fileapp.FileApp to make it
support GET and HEAD properly. If you subclassed FileApp or DataApp you
may need to change your code.
* Parsing of Accept and Accept-Language
* paste.wsgiwrappers.WSGIRequest can optionally decode unicode values in
* paste.httpserver supports all request methods (e.g., MKCOL), no longer
blocks if you read past the end of wsgi.input, and includes code to
control the thread pool and kill threads that are wedged.
Ian Bicking | ianb(a)colorstudy.com | http://blog.ianbicking.org