Mailman 3 December 2004 - Python-announce-list

PyJuggler 1.0 Beta 1 available
by Patrick Hartling 29 Dec '04

29 Dec '04

Following up on the release of VR Juggler 2.0 Beta 1, I am pleased to announce the release of PyJuggler 1.0 Beta 1. This release includes many important additions over the last release in July 2004: 1) Complete code coverage for user-visible application programming interfaces 2) Addition of bindings for vrj::GlContextData<T> to allow for user-defined application-specific data in Python application objects 3) Addition of bindings for cluster::UserData<T> to allow for user-defined shared data types in cluster configurations 4) Addition of docstrings for all classes and nearly all methods and functions 5) Support for Mac OS X (without PyJuggler.vrj.OsgApp, however) 6) Support for pickling of types commonly used with application-specific shared data in cluster configurations 7) Addition of bindings for Sonix in the new module PyJuggler.snx For more information and downloads, go to the PyJuggler website: http://www.vrjuggler.org/pyjuggler/ The full source code and binary versions of PyJuggler for Fedora Cora 2 and Microsoft Windows (Visual C++ 7.1) can be downloaded from this page: http://www.vrjuggler.org/pyjuggler/download.php I will be posting a build for Mac OS X 10.3 (Panther) later today or tomorrow once I get an installer created. For more details on 2), 3), and 6) from above, refer to the updated and extended PyJuggler /Getting Started Guide/ on the PyJuggler documentation page: http://www.vrjuggler.org/pyjuggler/docs.php The pydoc-generated API documentation is available with the pre-compiled releases and from the PyJuggler documentation page. All pre-compiled releases include a compiled version of PyGMTL 0.4.5, which includes pickling support for all GMTL data types. A pre-compiled copy of Boost.Python from Boost 1.32.0 comes with the VR Juggler 2.0 Beta 1 dependencies. It is highly recommended that the dependency distribution be used. The package for your platform and compiler can be acquired here: http://sourceforge.net/project/showfiles.php?group_id=8041&package_id=11700… Please note that the pre-compiled versions of PyJuggler for Fedora Core 2 and Windows were built against Python 2.3 and Open Scene Graph 0.9.8. If you are using Python 2.4, you will have to build Boost.Python and PyJuggler yourself (it will work just fine). If you are using OSG 0.9.7, you will have to rebuild PyJuggler against that version. If you are not using OSG at all, do not worry about this detail. The access to PyJuggler.vrj.OsgApp through PyJuggler is optional, and its availability is determined at run time. What is PyJuggler? ------------------ PyJuggler is an extension to VR Juggler I started in my spare time one weekend in November 2002. Its main purpose is to fulfill a goal I have had for a long time: the ability to write VR Juggler application objects in a scripting language. In this case, the language is Python, a mature and popular object-oriented scripting language. Using PyJuggler, it is possible to write a VR Juggler application object in Python and load the object into the VR Juggler kernel, which of course is written in C++. Python-based application objects can even be mixed with C++ application objects in the same kernel. Lastly, it is possible to write the equivalent of a C++ main() function in Python so that a developer need never see or write any C++ code to use VR Juggler. PyJuggler is built on top of the excellent Boost.Python v2 library (http://www.boost.org/libs/python/). Boost.Python makes the mapping between C++ and Python quite simple. It also makes embedding Python in C++ vastly easier than was previously possible. Current Status -------------- The support for Mac OS X is new in this release. Getting PyJuggler to work on Mac OS X required improving the way in which the VR Juggler libraries are compiled and linked. To do this, I took advantage of all the work the Boost developers and users did to get Boost compiling and working well on Mac OS X. Nevertheless, there is probably still room to improve the use of PyJuggler on Mac OS X. Known Problems -------------- At this time, third-party dependencies such as omniORB and Open Scene Graph are not getting along with PyJuggler on Mac OS X. Therefore, PyOSG cannot be used with PyJuggler on Mac OS X, and the CORBA-based features of the VR Juggler C++ code base are not available through PyJuggler. All other platforms are working fine. -Patrick -- Patrick L. Hartling | VP Engineering, Infiscape Corp. PGP: http://tinyurl.com/2msw3 | http://www.infiscape.com/

1 1

ANN: PyEnchant 0.9.1
by Ryan Kelly 29 Dec '04

29 Dec '04

PyEnchant version 0.9.1 has been released. Updates include: * Windows installer with self-contained copy of enchant library and ispell dictionaries * Confirmed to work with latest Enchant release Most importantly, it now provides a click-to-install spellchecking solution for python on the windows platform. It should work using the system enchant library anywhere that enchant itself can run. About: ------- Enchant (http://www.abisource.com/enchant/) is the spellchecking package behind the AbiWord word processor, is being considered for inclusion in the KDE office suite, and is proposed as a FreeDesktop.org standard. It's completely cross-platform because it wraps the native spellchecking engine to provide a uniform interface. PyEnchant brings this simple, powerful and flexible spellchecking engine to Python: http://www.rfk.id.au/software/projects/pyenchant/ Current Version: 0.9.1 Licence: LGPL with exemptions, as per Enchant itself Cheers, Ryan

1 0

Reminder: PyCon 2005 CFP
by A.M. Kuchling 27 Dec '04

27 Dec '04

This coming Friday, December 31st, is the deadline for proposals for PyCon 2005. If you've been procrastinating about getting your proposal outline done, time is running short... Call for proposals: http://www.python.org/pycon/2005/cfp.html Proposal submission site: http://submit.pycon.org --amk

1 0

Chennai, India - Python Meetup
by Sridhar R 26 Dec '04

26 Dec '04

Join the club here http://python.meetup.com/144/

1 0

Please Donate to the PSF
by Stephan Deibel 25 Dec '04

25 Dec '04

Hi, As the holiday season ends and a new year approaches, I would like to take this opportunity to thank everyone that donated to the Python Software Foundation (PSF) in the past. Everyone's support is greatly appreciated. We now have well over 400 donors, many of whom donate regularly: http://www.python.org/psf/donations.html We also have 15 sponsor members that contribute annually to the PSF: http://www.python.org/psf/ Because of our donors and sponsors, the PSF was able to issue its first grants solicitation in 2004. This was very successful, with many more quality submissions than we could fund. Several grants have been approved for completion in 2005. With these and future grants, we intend to continue improving Python. The PSF also manages the intellectual property rights behind Python and runs the PyCon developers conference annually: http://www.python.org/pycon/ Please consider donating in order to support Python and the PSF. We are currently accepting donations via check or PayPal, and will soon begin accepting credit cards directly. Donations can be made starting here: http://www.python.org/psf/donations.html The PSF is a registered 501(c)(3) charity so donations are tax-deductible for US tax payers. There is still time to make a donation that can be deducted in the 2004 tax year. If you would like to learn more about the PSF, please visit: http://www.python.org/psf/ Happy New Year! Sincerely, Stephan Deibel Chairman of the Board Python Software Foundation http://python.org/psf

1 0

Dr. Dobb's Python-URL! - weekly Python news and links (Dec 25)
by Josiah Carlson 25 Dec '04

25 Dec '04

QOTW: "Python, the language that wraps tightly around a problem and swallows it whole." -- Raymond Hettinger Because it is so important, this link is re-posted for the future (originally appeared in the December 15 Python-Url! posting by Cameron Laird): Martin Bless summarizes in an extremely valuable post what you need to know to generate Python-related executable binaries targeted for Windows*. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/7… Mark English asks about running a tk GUI using a background thread. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/1… You can register for PyCon DC 2005 on the web. http://www.python.org/pycon/2005/register.html A reminder to those who don't restart their editors while running their scripts: you are probably looking for reload(). http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/9… Pointers to a handful of "graphics drawing" toolkits, hopefully to result in a learning tool for sorting algorithms in Python. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/f… Importing binary modules from ZIPs by Thomas Heller. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/b… For the masochistic among us, a 120+ message thread on the history of BASIC, Python, and why BASIC is probably not the first language one should learn. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/5… timbot exhibits a concrete instance of the long-conjectured universal follow-up, that is, a post which mis-answers all confusion equally well. Merry Christmas to you, too. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/a… Diez B. Roggisch asks about decorator peculiarities and receives a clarified version of his decorators in function and class form. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/0… Mike Meyer proposes a rational number module for Python. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/2… Stephen Kellet announces a thread and lock validation tool for Python and its test-oriented fans. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/6… SPE version 0.7.0.a is released. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/d… PythonCAD 20 appears. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/a… Python is now available on NokiaS60 phones. http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/4… ======================================================================== Everything Python-related you want is probably one or two clicks away in these pages: Python.org's Python Language Website is the traditional center of Pythonia http://www.python.org Notice especially the master FAQ http://www.python.org/doc/FAQ.html PythonWare complements the digest you're reading with the marvelous daily python url http://www.pythonware.com/daily Mygale is a news-gathering webcrawler that specializes in (new) World-Wide Web articles related to Python. http://www.awaretek.com/nowak/mygale.html While cosmetically similar, Mygale and the Daily Python-URL are utterly different in their technologies and generally in their results. comp.lang.python.announce announces new Python software. Be sure to scan this newsgroup weekly. http://groups.google.com/groups?oi=djq&as_ugroup=comp.lang.python.announce Brett Cannon continues the marvelous tradition established by Andrew Kuchling and Michael Hudson of intelligently summarizing action on the python-dev mailing list once every other week. http://www.python.org/dev/summary/ The Python Package Index catalogues packages. http://www.python.org/pypi/ The somewhat older Vaults of Parnassus ambitiously collects references to all sorts of Python resources. http://www.vex.net/~x/parnassus/ Much of Python's real work takes place on Special-Interest Group mailing lists http://www.python.org/sigs/ The Python Business Forum "further[s] the interests of companies that base their business on ... Python." http://www.python-in-business.org Python Success Stories--from air-traffic control to on-line match-making--can inspire you or decision-makers to whom you're subject with a vision of what the language makes practical. http://www.pythonology.com/success The Python Software Foundation (PSF) has replaced the Python Consortium as an independent nexus of activity. It has official responsibility for Python's development and maintenance. http://www.python.org/psf/ Among the ways you can support PSF is with a donation. http://www.python.org/psf/donate.html Kurt B. Kaiser publishes a weekly report on faults and patches. http://www.google.com/groups?as_usubject=weekly%20python%20patch Cetus collects Python hyperlinks. http://www.cetus-links.org/oo_python.html Python FAQTS http://python.faqts.com/ The Cookbook is a collaborative effort to capture useful and interesting recipes. http://aspn.activestate.com/ASPN/Cookbook/Python Among several Python-oriented RSS/RDF feeds available are http://www.python.org/channews.rdf http://bootleg-rss.g-blog.net/pythonware_com_daily.pcgi http://python.de/backend.php For more, see http://www.syndic8.com/feedlist.php?ShowMatch=python&ShowStatus=all The old Python "To-Do List" now lives principally in a SourceForge reincarnation. http://sourceforge.net/tracker/?atid=355470&group_id=5470&func=browse http://python.sourceforge.net/peps/pep-0042.html The online Python Journal is posted at pythonjournal.cognizor.com. editor(a)pythonjournal.com and editor(a)pythonjournal.cognizor.com welcome submission of material that helps people's understanding of Python use, and offer Web presentation of your work. *Py: the Journal of the Python Language* http://www.pyzine.com Archive probing tricks of the trade: http://groups.google.com/groups?oi=djq&as_ugroup=comp.lang.python&num=100 http://groups.google.com/groups?meta=site%3Dgroups%26group%3Dcomp.lang.pyth… Previous - (U)se the (R)esource, (L)uke! - messages are listed here: http://www.ddj.com/topics/pythonurl/ http://purl.org/thecliff/python/url.html (dormant) or http://groups.google.com/groups?oi=djq&as_q=+Python-URL!&as_ugroup=comp.lan… Suggestions/corrections for next week's posting are always welcome. E-mail to <Python-URL(a)phaseit.net> should get through. To receive a new issue of this posting in e-mail each Monday morning (approximately), ask <claird(a)phaseit.net> to subscribe. Mention "Python-URL!". -- The Python-URL! Team-- Dr. Dobb's Journal (http://www.ddj.com) is pleased to participate in and sponsor the "Python-URL!" project.

1 0

Upcoming PyPy sprint
by Armin Rigo 25 Dec '04

25 Dec '04

Hi Python people, The next sprint for PyPy, the Python-in-Python interpreter, will take place in Leysin, in the lower mountains of Switzerland, 22nd - 29th January 2005 (travel days: 22nd and 29-30th) http://codespeak.net/moin/pypy/moin.cgi/LeysinSprint The technical goals will be two-fold: we want to continue the hard work started at the previous Vilnius sprint (a first generated C version of our interpreter); but the upcoming sprint will also be a "learning PyPy" sprint, covering all aspects of PyPy that are easier to start with. Some examples are described below. For more information about PyPy, see http://codespeak.net/pypy/index.cgi?doc . The "learning PyPy" focus comes from the fact that it will be our first sprint as a European Union sponsored group, and not all members of this EU/PyPy project are already familiar with PyPy. This is a good occasion for newcomers that want to look at PyPy more closely too, in a "fun and somewhat mind-altering" sprint event. Note that as part of our funding we want to be able to support some of the travel and lodging costs for a number of outside people as well, but although the corresponding money is in the budgets, not all administrative issues have been solved yet. We don't know yet if we will be able to do so for the January sprint. However, if you would like to come to the sprint but can't afford travel and accomodation costs then please contact us. Even if the administrative issues have not been sorted out, we may be able to help with private money. Just contact us or me personally for this sprint. About Leysin ------------ The place where the sprint will take place is located in the pre-Alps of the french-speaking (west) region of Switzerland. Leysin is a village at an altitude of 1200 to 1400m. It is a skiing station, and also the place where I (Armin) lived for 20 years. There are 2000 people in summer and 10000 in winter :-) but the sprint will be just before the most crowded periods of February. Of course one full day will be dedicated to winter sports! Both the sprint venue and the logding will be in a very spacious pair of chalets built specifically for bed&breakfast: http://www.ermina.ch/. The place has a baseline ADSL Internet connexion (600Kb); we need to arrange between ourselves to bring a wireless hub. You can of course arrange your own lodging anywhere (you cannot be more than a 15 minutes walk away from the sprint venue), but I definitely recommend to lodge there too -- you won't find better sights anywhere else (though you probably won't get much worse ones easily, either :-) Subscription ------------ Please subscribe at http://codespeak.net/moin/pypy/moin.cgi/LeysinSprintAttendants and mention if you would like to participate in the group reservation, and which size of room you would prefer (2 to 6 beds available). If you wish, you can extend your stay for some days after the 29th of January -- please mention it if you want to book with the group (but you cannot arrive there earier than the 22nd: fully booked). If you have any question don't hesitate to contact pypy-sprint(a)codespeak.net or one of us personally. Learning PyPy ------------- Here are some goals that are quite reachable without in-depth prior knowledge of PyPy: * systematic testing: the interpreter and type implementations work generally well, but there are quite some areas that need refactoring and refinement. A good approach is to run as many of CPython's tests as possible and fix stuff accordingly. This is a good way to learn random parts of PyPy until you know them all! * extension modules and extension types: some can be just rewritten as a plain Python equivalent, but others need to be more integrated into PyPy's internals. * the bytecode compiler: we don't have any compiler integrated with PyPy so far, but there exists a complete set of Python code out there (tokenizer, parser, st->ast, ast->bytecode) that could be used. We could also discuss ideas like syntax extensions generating new bytecodes, etc. * tracing and other wrappers: e.g. how to write a fully debugging Object Space that records the history of all changes to objects, etc. * more bits and pieces: small things missing from our interpreter to be fully compliant. Tracing/profiling hooks come to mind; more small things are listed in http://codespeak.net/svn/pypy/trunk/src/pypy/TODO . In addition to the above examples, there are a number of more involved tasks that nevertheless don't require a complete grasp of PyPy -- whose parts are relatively independent from each other. The "hard" work currently going on in PyPy is on the translation part, which is needed to make PyPy run faster and/or in other environments. This work is however mostly independent. For people that prefer to focus on cross-language stuff rather than Python internals we can discuss about tasks like writing the basics of an interpreter for another language -- for example, it would be great to have a decent error-checking Javascript interpreter, but we can discuss any other language, Python-like or not. In parallel, there is always pending work to allow the code generator to target other languages and platforms (currently there is C, Lisp, Pyrex and Java) or generate code differently (Stackless-style, Psyco-style). A bientot, Armin Rigo

1 0

python-dev Summary for 2004-11-01 through 2004-11-15
by Brett C. 24 Dec '04

24 Dec '04

python-dev Summary for 2004-11-01 through 2004-11-15 ++++++++++++++++++++++++++++++++++++++++++++++++++++ This is a summary of traffic on the `python-dev mailing list`_ from November 01, 2004 through November 15, 2004. It is intended to inform the wider Python community of on-going developments on the list. To comment on anything mentioned here, just post to `comp.lang.python`_ (or email python-list(a)python.org which is a gateway to the newsgroup) with a subject line mentioning what you are discussing. All python-dev members are interested in seeing ideas discussed by the community, so don't hesitate to take a stance on something. And if all of this really interests you then get involved and join `python-dev`_! This is the fifty-second summary written by Brett Cannon (Happy Holidays). To contact me, please send email to brett at python.org ; I do not have the time to keep up on comp.lang.python and thus do not always catch follow-ups posted there. All summaries are archived at http://www.python.org/dev/summary/ . Please note that this summary is written using reStructuredText_ which can be found at http://docutils.sf.net/rst.html . Any unfamiliar punctuation is probably markup for reST_ (otherwise it is probably regular expression syntax or a typo =); you can safely ignore it, although I suggest learning reST; it's simple and is accepted for `PEP markup`_ and gives some perks for the HTML output. Also, because of the wonders of programs that like to reformat text, I cannot guarantee you will be able to run the text version of this summary through Docutils_ as-is unless it is from the `original text file`_. .. _PEP Markup: http://www.python.org/peps/pep-0012.html The in-development version of the documentation for Python can be found at http://www.python.org/dev/doc/devel/ and should be used when looking up any documentation on new code; otherwise use the current documentation as found at http://docs.python.org/ . PEPs (Python Enhancement Proposals) are located at http://www.python.org/peps/ . To view files in the Python CVS online, go to http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/ . Reported bugs and suggested patches can be found at the SourceForge_ project page. The `Python Software Foundation`_ is the non-profit organization that holds the intellectual property for Python. It also tries to forward the development and use of Python. But the PSF_ cannot do this without donations. You can make a donation at http://python.org/psf/donations.html . Every penny helps so even a small donation (you can donate through PayPal or by check) helps. .. _python-dev: http://www.python.org/dev/ .. _SourceForge: http://sourceforge.net/tracker/?group_id=5470 .. _python-dev mailing list: http://mail.python.org/mailman/listinfo/python-dev .. _comp.lang.python: http://groups.google.com/groups?q=comp.lang.python .. _Docutils: http://docutils.sf.net/ .. _reST: .. _reStructuredText: http://docutils.sf.net/rst.html .. _PSF: .. _Python Software Foundation: http://python.org/psf/ .. contents:: .. _last summary: http://www.python.org/dev/summary/2004-10-16_2004-10-31.html .. _original text file: http://www.python.org/dev/summary/2004-11-01_2004-11-15.ht ===================== Summary Announcements ===================== I am hoping to be caught up with my summary backlog by the end of the month. Here is to hoping. ========= Summaries ========= ------------ 2.4 released ------------ `Python 2.4`_ has been released! Read the `What's New`_ for 2.4 to see what the major changes are since 2.3 . .. _Python 2.4: http://www.python.org/2.4/ .. _What's New: http://www.python.org/doc/2.4/whatsnew/whatsnew24.html Contributed threads: - `TRUNK FROZEN for 2.4b2 release from 0000UTC 3rd November (tomorrrow) <http://mail.python.org/pipermail/python-dev/2004-November/049736.html>`__ - `RELEASED Python 2.4, beta 2 <http://mail.python.org/pipermail/python-dev/2004-November/049754.html>`__ - `TRUNK UNFROZEN <http://mail.python.org/pipermail/python-dev/2004-November/049762.html>`__ ------------------------------------- Code coverage of the regression tests ------------------------------------- Walter Dörwald has a code coverage tool that runs once a month on Python's regression test at http://coverage.livinglogic.de/ . There was some issue with the 'trace' module having partially broken in 2.4 . The coverage was then run using ``Lib/test/regrtest.py -T`` to get more accurate numbers. Contributing threads: - `Code coverage tool updated <http://mail.python.org/pipermail/python-dev/2004-November/049727.html>`__ ------------------------------------ Garbage collecting weakref callbacks ------------------------------------ Tim Peters discovered that in 2.4 if a weakref's callback is still reachable but the referent and weakref itself are unreachable (Tim's example had an instance that contained a weakref to itself) that the callback is not called during garbage collection. This seemed inconsistent since if the weakref in Tim's example was replaced with an instance that contained a __del__ method that the method would have been called. Tim would like to clean this up so as to be able to ditch __del__ methods in Python 3000. The idea is that one would register a weakref with a callback for an object in itself that would be called when it is garbage collected. This would also negate the need for gc.garbage . Contributing threads: - `weakref gc semantics <http://mail.python.org/pipermail/python-dev/2004-November/049744.html>`__ - `patch-finalizer vs Zope3 <http://mail.python.org/pipermail/python-dev/2004-November/049774.html>`__ --------- PEP Watch --------- `PEP 336`_ introduces the idea of having None be a callable object. The result of calling None would return None itself. .. _PEP 336: http://www.python.org/peps/pep-0336.html Contributing threads: - `PEP 336, "Make None Callable", by Andrew McClelland <http://mail.python.org/pipermail/python-dev/2004-November/049760.html>`__ ---------------------------------------------- Discussion of including pysqlite in the stdlib ---------------------------------------------- The idea of including pysqlite_ in the stdlib came up once again (note this is the wrapper for SQLite_ and not SQLite itself). The arguments for including the module were that SQLite is most likely used more than Sleepycat and thus deserved a place in the stdlib if bsddb did. It also goes along with Python's idea of "batteries included". Arguments against the proposal started with the idea that sanctioning pysqlite over other SQLite wrappers was improper. People also thought that including bsddb might not be correct anymore and thus should not be used as a basis for including pysqlite. This all then led into a discussion about package management and how to simplify extending what can be installed at compile-time. The idea of pushing PyPI_ came up as well as revising `PEP 206`_. .. _pysqlite: http://pysqlite.org/ .. _SQLite: http://www.sqlite.org/ .. _PyPI: http://www.python.org/pypi .. _PEP 206: http://www.python.org/peps/pep-0206.html Contributing threads: - `SQLite module for Python 2.5 <http://mail.python.org/pipermail/python-dev/2004-October/049534.html>`__ -------------------------------- 2.3 maintenance coming to an end -------------------------------- With Python 2.4 out, maintaining 2.3 is no longer a priority. Anthony Baxter, our beloved release manager, has said that 2.3.5 will be most likely coming out in January. After that, though, don't count on another 2.3 release since 2.4 will take its place as the version to maintain. All of this came about by the fact that Facundo Batista asked if closing 2.1 bugs was okay. As long as they have been fixed in the earliest version being maintained, closing them is fine. This goes for 2.2 as well. And as soon as 2.3.5 is released this will most likely apply to 2.3 bugs. Contributing threads: - `Policy about old Python versions <http://mail.python.org/pipermail/python-dev/2004-November/049769.html>`__ ----------------------------------------------------------------- Sync/async servers in the stdlib and whether they should be there ----------------------------------------------------------------- There are multiple servers in the core for handling communications in both a synchronous and asynchronous manner. The idea came up of developing an API that all servers could follow in the core. While the discussion went back and forth with multiple mentions of PEAK, Twisted, and greenlets_, in the end the trend of the discussion suggested doing this well would be very difficult and not worth the effort. asyncore and asynchat also seemed to be deemed worth deprecation and thus not worth using. .. _PEAK: http://peak.telecommunity.com/ .. _Twisted: http://www.twistedmatrix.com/ .. _greenlets: http://codespeak.net/svn/user/arigo/greenlet/ Contributing threads: - `Synchronous and Asynchronous servers in the standard library <http://mail.python.org/pipermail/python-dev/2004-November/049815.html>`__ -------------------------------------------------- Getting the opcode count for rough profile numbers -------------------------------------------------- The idea was proposed of introducing sys.gettickeraccumulation which would contain the number of opcodes executed since the interpreter started. The idea is that you can get a rough estimate of how much time is being spent in Python code. The value of this has wavered back and forth with no clear answer. If it does get included it will not be on by default. Contributing threads: - `proposal+patch: sys.gettickeraccumulation() <http://mail.python.org/pipermail/python-dev/2004-November/049893.html>`__ =============== Skipped Threads =============== - Deprecate PyRange_New() - interlocking dependencies on the path to a release see the first email to see what steps are needed for a release - Overflow in socketmodule.c? - Int literals and method calls To get access to methods on an int literal put a space after the number; ``1 .__class__`` - os.access versus os.exist - syntactic shortcut - unpack to variably sized list don't expect syntactic support variable-length sequences ain't happenin'

1 0

Docutils 0.3.7 released
by Felix Wiemann 24 Dec '04

24 Dec '04

Docutils 0.3.7 released ======================= Docutils 0.3.7 has been released. You can download it from <http://prdownloads.sf.net/docutils/docutils-0.3.7.tar.gz?download>. The Docutils homepage is located at <http://docutils.sf.net/>. Docutils is a system for processing plaintext documentation into various useful formats, such as HTML or LaTeX. It includes reStructuredText, the easy to read, easy to use, what-you-see-is-what-you-get plaintext markup language. Major changes since Docutils 0.3.5: * A special "line block" syntax useful for addresses, verse, and other cases of significant line breaks has been added; see <http://docutils.sf.net/docs/user/rst/quickref.html#line-blocks> and <http://docutils.sf.net/docs/ref/rst/restructuredtext.html#line-blocks>. * Empty sections are now allowed. * A "raw" role has been added; see <http://docutils.sf.net/docs/ref/rst/roles.html#raw>. * The LaTeX writer now escapes consecutive dashes (like "--" or "---") so that they are no longer transformed by LaTeX to en or em dashes. If you want to write en or em dashes using pure ASCII, please refer to <http://docutils.sf.net/FAQ.html#how-can-i-represent-esoteric-characters-e-g…>. * A dependency recorder has been added; see <http://docutils.sf.net/docs/user/config.html#record-dependencies>. * A directive has been added for compound paragraphs; see <http://docutils.sf.net/docs/ref/rst/directives.html#compound-paragraph>. * Many other improvements and bug fixes; see <http://docutils.sf.net/0.3.7/HISTORY.html>. Merry Christmas! -- Felix Wiemann -- http://www.ososo.de/

1 0

IMDbPY 1.5 released
by alberanid＠libero.it 23 Dec '04

23 Dec '04

IMDbPY 1.5 is available (tgz, deb, rpm) from: http://imdbpy.sourceforge.net/ IMDbPY is a Python package useful to retrieve and manage the data of the IMDb movie database. This release introduces support for the local installation of the IMDb's database. Some bugs have been fixed. IMDbPY aims to provide an easy way to access the IMDb's database using a Python script. Platform-independent and written in pure Python, it's independent from the data source (since IMDb provides two or three different interfaces to their database). IMDbPY is mainly intended for programmers and developers who want to build their Python programs using the IMDbPY package, but some example scripts - useful for simple users - are included. -- Davide Alberani <alberanid(a)libero.it> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/

1 0