Düsseldorf PyPy sprint November 6 - November 13 2009
=====================================================
The next PyPy sprint will be held in the Computer Science department of
Heinrich-Heine Universität Düsseldorf from the 6th to the 13th of
November 2009. This is a fully public sprint, everyone is welcome to
join us.
Topics and goals
----------------
At the sprint we intend to work on the JIT generator in PyPy and on
applying it to PyPy Python interpreter.
The precise work that will be done is not fixed, as we don't know in
which state the JIT will be in November. However, possible areas of
work might include:
- tweaking the interpreter/objspace to be more JIT-friendly, e.g.
instance implementation code, call code
- if there is interest starting non x86-32 JIT backends
- trying out existing software to find features where the optimizations
of the JIT could be improved
- improving our benchmarking infrastructure
We will give special priority to topics that "non-core" people find
interesting (as long as they are somehow JIT-related).
For an introduction of how our JIT-generation process works, please
refer to our blog:
http://morepypy.blogspot.com/2009/03/jit-bit-of-look-inside.html
There is also a more dense academic paper about the subject:
http://codespeak.net/svn/pypy/extradoc/talk/icooolps2009/bolz-tracing-jit-f…
Location
--------
The sprint will take place in a seminar room of the computer science
department. It is in the building 25.12 of the university campus. For
travel instructions see
http://stups.cs.uni-duesseldorf.de/anreise/esbahn.php
Registration
------------
If you'd like to come, please subscribe to the `pypy-sprint mailing
list`_ and drop a note about your interests and post any questions.
More organisational information will be send to that list. We'll keep a
list of `people`_ which we'll update (which you can do so yourself if
you have codespeak commit rights).
.. _`pypy-sprint mailing list`:
http://codespeak.net/mailman/listinfo/pypy-sprint
.. _`people`:
http://codespeak.net/pypy/extradoc/sprintinfo/ddorf2009/people.txt
python-fedex 1.0 has been released. This GPLv3 module is a very light
wrapper around the excellent suds SOAP module and FedEx's Web Services
WSDLs. The purpose of this module is to prepare the WSDL objects for
the user to populate and manipulate as needed, as well as handling
sending and light processing for common errors. python-fedex leaves
the user to read FedEx's documentation to understand all of the fields
exposed by python-fedex.
Requirements:
* Python 2.5+, but not 3.0
* suds (https://fedorahosted.org/suds/)
Download:
http://code.google.com/p/python-fedex/
A fast portable pure-python multithreaded experimental WSGI web server
in 300 lines of code:
Python 2.4,2.5,2.6 version:
http://code.google.com/p/web2py/source/browse/trunk/gluon/sneaky.py
Python 3.0,3.1 version:
http://code.google.com/p/web2py/source/browse/trunk/gluon/
sneaky3.py
1) Some third party benchmarks are in the doc strings but you should
run them yourself. These are benchmarks for the servers, not the
frameworks.
2) We are not sure it is perfectly WSGI compliant but it is very
similar to Cherrypy wsgiserver 3.2.
3) Experimental means we are still ironing down WSGI compliance and we
have not tested chunked uploads (only regular uploads).
4) This is distributed with web2py, it works with web2py, but until we
have more tests done, web2py still uses cherrypy's wsgi server in
production.
5) The license is GPL but we are going change it to MIT of BSD or
Apache when done.
6) We are posting here because we hope you will give it a try and
report compatibility issues with your favorite framework and browser.
This will help us fix problems and turn into a fast production server.
On behalf of the Jython development team, I'm pleased to announce that
Jython 2.5.1rc3 is available for download here:
https://sourceforge.net/projects/jython/files/jython-dev/2.5.1rc3/jython_in…
- See http://wiki.python.org/jython/InstallationInstructions for
installation instructions.
I didn't really want to have an RC3, I was hoping to have a final by
now, but a data loss bug was discovered in RC2 and that prompted one
more RC. I'm hoping that this is the last one and that we'll have a
final shortly. Please see the NEWS file for detailed release notes.
Please report any bugs that you find here: http://bugs.jython.org
Thanks,
-Frank
I am pleased to announce version 2.20.0 of the Python bindings for GObject.
The new release is available from ftp.gnome.org as and its mirrors
as soon as its synced correctly:
http://download.gnome.org/sources/pygobject/2.20/
What's new since PyGObject 2.19.0?
- Allow to use automake 1.11 (Paolo Borelli)
- Specify programming language in .devhelp file (Frédéric Péters)
- Plug reference leak of GSource in pyg_main_loop_init (Paul)
- Updated uninstalled.pc file (Brian Cameron)
Blurb:
GObject is a object system library used by GTK+ and GStreamer.
PyGObject provides a convenient wrapper for the GObject library for use
in Python programs, and takes care of many of the boring details such as
managing memory and type casting. When combined with PyGTK, PyORBit and
gnome-python, it can be used to write full featured Gnome applications.
Like the GObject library itself PyGObject is licensed under the
GNU LGPL, so is suitable for use in both free software and proprietary
applications. It is already in use in many applications ranging
from small single purpose scripts up to large full
featured applications.
PyGObject requires glib >= 2.14.0 and Python >= 2.3.5 to build.
GIO bindings require glib >= 2.16.0.
cheers
--
Gian Mario Tagliaretti
GNOME Foundation member
gianmt(a)gnome.org
CodeInvestigator version 0.16.0 was released on Sept 23.
It requires Python version 2.6 and a Firefox browser.
Bug fixes:
Indentation of comments and triple quoted strings. Triple quoted
strings
could embed additional spaces.
Additional __str__ calls were made for an instance.
Record scripts that don't have a .py extension.
ELIF sometimes fails.
Docstrings passed over to generated program
Issue with importing 64 bit modules
Initial syntax check sometimes rejected too much.
Thanks Tim!
Changes: Remarks.
If you click in the right margin you can enter remarks.
Remarks can be dragged to another location if you use Firefox
3.5.
They are intended to work like poste-it notes attached to a
printout of the
code.
Warning:
The database will be initialized and you will lose your runs.
CodeInvestigator is a tracing tool for Python programs.
Running a program through CodeInvestigator creates a recording.
Program flow, function calls, variable values and conditions are all
stored for every line the program executes.
The recording is then viewed with an interface consisting of the
code. The code can be clicked: A clicked variable displays its
value,
a clicked loop displays its iterations.
You read code, and have at your disposal all the run time details of
that code. A computerized desk check tool and another way to learn
about your program.
http://sourceforge.net/project/showfiles.php?group_id=183942
Hi All,
I'm pleased to announce a new release of TestFixtures.
This package is a collection of helpers and mock objects that are useful
when writing unit tests or doc tests.
This release fixes problems when using Comparison objects with instances
of Django models, so tests like the following will now work as expected:
from testfixtures import Comparison as C,compare
class TestUser(TestCase):
def test_create(self):
u = User(name='Test')
u.save()
t = User.objects.get(name='Test')
compare([C(User,name='Test',strict=False)],
list(User.objects.all()))
To find out more, please read here:
http://pypi.python.org/pypi/testfixtures
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
Hello Python Community,
We're pleased to announce the release of IronPython 2.6 Release Candidate 1 which can be freely downloaded at http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=30315. Over the development span of IronPython 2.6, exactly 417 bugs have been fixed. Since the release of Beta 2, we've addressed the following:
* Non-hosting related APIs previously found in Microsoft.Scripting.dll have been migrated to Microsoft.Dynamic.dll. The rationale behind this decision is that we're aiming for compatible DLR binaries with the next major release of IronRuby, namely 1.0. Microsoft.Dynamic.dll will likely end up being a bit different between IronPython 2.6 and IronRuby 1.0, but we intend on keeping Microsoft.Scripting.dll and Microsoft.Scripting.Core.dll exactly the same. By doing this you'll be able to utilize the DLR hosting APIs to run both IronPython 2.6 and IronRuby 1.0 code from the same .NET application!
* Documentation distributed with the release has been updated
* A plethora of bugs have been fixed over the past two months with special emphasis given to CodePlex work items with lots of votes
If no major issues with this release candidate are discovered, we hope to ship the final 2.6 release in a little under a month. Anyone planning on upgrading to 2.6 should try out this release candidate and let us know of any issues you find ASAP.
Thanks to everyone in the IronPython Community who reported bugs and provided valuable feedback: Zachc, yamakox, vernondcole, VAks, tscottw, tonyandrewmeyer, tomwright, TomasMatousek, tkamiya, timers, srivatsn, sopeajw, saveenr, sanxiyn, rridge, ronniemaor, quirogaco, pythonfoo, py_sunil, pm100, pl6306, paulfelix, orestis, olegt, oldman, NDHUMuscle, mycall, mmaly, mmacdonaldssfcu, maplpro, luntain, llaske, lbaker, Lawouach, laurionb, laughingboy, kurhan, kuno, kowenswp, klrohe, kevgu, jmesserly, jlunder, jdhardy, jbevain, jackeyoo, hhonisch, gz, gjones, fwereade, deadalusai, daveremy, darb, CurtHagenlocher, chaghi, cgravill, cartman, bobarnso, billchi, atifaziz, ashcor, alvanet, __Helmut__, fuzzyman, fabiofz, Eloff, egonw_, dungen, dsblank, dmajnemer, dinov, and dfugate.
We really do appreciate your input which helps to make every release of IronPython better than the last.
The IronPython Team
On behalf of the TurboGears Team, I am pleased to announce that
TurboGears 1.1rc1 is available for download at
http://turbogears.org/
and the Python package index
http://pypi.python.org/pypi/TurboGears
TurboGears 1.1rc1 is the first release candidate for the upcoming 1.1
release, which is the evolution of the TurboGears 1 codebase. The 1.1
branch now uses SQLAlchemy as the default database layer and Genshi as
the standard templating engine but is 100 percent compatible with
applications built on TurboGears 1.0.
We encourage you to test this release with your existing TurboGears 1.0
applications and by building new ones. If no major problems are
reported, this release will become 1.1final in about two weeks. Beta
versions of TurboGears 1.1 have been in use in production environments
for over a year now, so we believe this release is rock-stable.
What is TurboGears?
-------------------
TurboGears is a rapid development, "front-to-back", open source web
meta-framework. Its aim is to simplify and speed up the development of
modern web applications written in the Python programming language.
TurboGears is designed around the model-view-controller architecture,
much like Struts or Ruby on Rails, and takes the best Python web
components available (hence "meta-framework") and combines them into one
easy-to-install, documented whole.
What's new?
-----------
Apart from the change of defaults to SLQAlchemy and Genshi, TurboGears
1.1 has a new testing framework built on WebTest, a new quickstart
design (backported from TurboGears 2) and many, many bigger and smaller
fixes and improvements over version 1.0 in its internals. For a
comprehensive list of changes see the changelog in our Trac at
http://trac.turbogears.org/wiki/ChangeLog
How to install?
---------------
The easiest way to install TurboGears 1.1rc1 is via setuptools:
[sudo] easy_install [-f http://turbogears.org/download/] TurboGears
we recommend that you install TurboGears into its own virtual
environment using the virtualenv tool:
[sudo] easy_install virtualenv
virtualenv --no-site-packages /path/to/tgenv
source /path/to/tgenv/bin/activate
easy_install [-f http://turbogears.org/download/] TurboGears
How is it related to TurboGears 2?
----------------------------------
TurboGears 1.1 is based on the original TurboGears 1.0 codebase and
still uses CherryPy 2.3 as the underlying web application server. It is
100 percent compatible with existing TurboGears 1.0 applications and
porting an application using SQLObject and Kid to use SQLAlchemy and
Genshi is easiliy achieved.
TurboGears 2 has almost the same API as TurboGears 1.x but builds on
Pylons as the underlying web engine. Most new development for TurboGears
now happens in version 2, but the 1.1 branch will be continued to be
supported and maybe even developed further for the foreseeable future.
The Future
----------
TurboGears 1.1 final is slated to be released in about two weeks.
Afterwards we plan to issue a maintenance release for the TurboGears 1.0
branch, which would be version 1.0.9.
Further development on the TurboGears 1.1 branch depends on community
feedback, which we plan to collect by conducting an online survey
amongst TurboGears users. You may expect a separate announcement for
this very soon!
Share & enjoy!
--
Christopher Arndt <sysadmin(a)turbogears.org>
TurboGears Systems Administrator
http://www.turbogears.org/
Hello!
I'm pleased to announce version 0.11.1, a minor bugfix release of 0.11 branch
of SQLObject.
What is SQLObject
=================
SQLObject is an object-relational mapper. Your database tables are described
as classes, and rows are instances of those classes. SQLObject is meant to be
easy to use and quick to get started with.
SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).
Where is SQLObject
==================
Site:
http://sqlobject.org
Development:
http://sqlobject.org/devel/
Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss
Archives:
http://news.gmane.org/gmane.comp.python.sqlobject
Download:
http://cheeseshop.python.org/pypi/SQLObject/0.11.1
News and changes:
http://sqlobject.org/News.html
What's New
==========
News since 0.11.0
-----------------
* Fixed a bug: Sybase tables with identity column fire two identity_inserts.
* Fixed a bug: q.startswith(), q.contains() and q.endswith() escape (with a
backslash) all special characters (backslashes, underscores and percent
signs).
For a more complete list, please see the news:
http://sqlobject.org/News.html
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ phd(a)phd.pp.ru
Programmers don't die, they just GOSUB without RETURN.