Mailman 3 March 2005 - Python-announce-list

Re: Online Programming Contest (Python solutions accepted)
by Sridhar R March 3, 2005

March 3, 2005

One important note about the contest: Top performers would be considered to join the 'Circle of Innovation' at Amazon India [1]. You may also have a chance to be considered for Internships/Externships/Work at Amazon India! Visit the contest page for more details: ** http://203.197.138.181/OPC ** [1] http://india.amazon.com/circle.php -- Sridhar Ratna - http://srid.bsdnerds.org

1 0

Re: Python Online Programming Contest
by Varun March 3, 2005

March 3, 2005

Hi, The results of OPC (online programming contest) is out. The statistics of python usage is available at http://www.samhita.info/opc/status.php Regards, -OPC Team

1 0

Roundup Issue Tracker release 0.8.2
by Richard Jones March 3, 2005

March 3, 2005

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roundup is a simple-to-use and -install issue-tracking system with command-line, web and e-mail interfaces. It is based on the winning design from Ka-Ping Yee in the Software Carpentry "Track" design competition. This 0.8.2 release adds one feature and fixes some bugs: Feature: - - roundup-server automatically redirects from trackers list to the tracker page if there is only one tracker Fixed: - - added content to ZRoundup refresh.txt file (sf bug 1147622) - - fix invalid reference to csv.colon_separated - - correct URL to What's New in setup.py meta-data - - change AUTOCOMMIT=OFF to AUTOCOMMIT=0 for MySQL (sf bug 1143707) - - compile message objects in 'setup.py build' - - use backend datatype for journal timestamps in RDBMSes - - fixes to the "Using an external password validation source" customisation example (sf bugs 1153640 and 1155108) If you're upgrading from an older version of Roundup you *must* follow the "Software Upgrade" guidelines given in the maintenance documentation. Roundup requires python 2.3 or later for correct operation. To give Roundup a try, just download (see below), unpack and run:: python demo.py Source and documentation is available at the website: http://roundup.sourceforge.net/ Release Info (via download page): http://sourceforge.net/projects/roundup Mailing lists - the place to ask questions: http://sourceforge.net/mail/?group_id=31577 About Roundup ============= Roundup manages a number of issues (with flexible properties such as "description", "priority", and so on) and provides the ability to: (a) submit new issues, (b) find and edit existing issues, and (c) discuss issues with other participants. The system will facilitate communication among the participants by managing discussions and notifying interested parties when issues are edited. One of the major design goals for Roundup that it be simple to get going. Roundup is therefore usable "out of the box" with any python 2.1+ installation. It doesn't even need to be "installed" to be operational, though a disutils-based install script is provided. It comes with two issue tracker templates (a classic bug/feature tracker and a minimal skeleton) and five database back-ends (anydbm, sqlite, metakit, mysql and postgresql). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCJpn9rGisBEHG6TARAiB/AJ9WYEySDgCMSrtHvkJmPZmCqOtXvQCaA1dv rLGfz4J5KWsxp5dcWeMfiNg= =zks0 -----END PGP SIGNATURE-----

1 0

ANNOUNCE: Kamaelia 0.1.1 Released
by Michael Sparks March 2, 2005

March 2, 2005

Kamaelia 0.1.1 has been released! This is the initial release version of Kamaelia. What is it? =========== Kamaelia is a collection of Axon components designed for network protocol experimentation in a single threaded, select based environment. Axon components are python generators are augmented by inbox and outbox queues (lists) for communication in a communicating sequential processes (CSP) like fashion. The architecture is specifically designed to try and simplify the process of designing and experimenting with new network protocols in real environments. This release contains components allowing the creation of TCP based clients and servers, and includes a few (very) simple protocol handlers to show usage. Other components include vorbis decode and playback, asynchronous file reading, and equivalents of "tee" and "strings". (Writing systems is much like building unix pipelines, hence the need for similar tools) Examples ======== Sample echo server: (default generator callback style) from Kamaelia.SimpleServerComponent import SimpleServer from Axon.Component import component, scheduler class EchoProtocolCB(component): def mainBody(self): if self.dataReady("inbox"): data = self.recv("inbox") self.send(data,"outbox") if self.dataReady("control"): data = self.recv("control") return 0 return 1 SimpleServer(protocol=EchoProtocolCB).activate() scheduler.run.runThreads(slowmo=0) Sample echo server: (Normal generator style) from Kamaelia.SimpleServerComponent import SimpleServer from Axon.Component import component, scheduler class EchoProtocol(component): def main(self): while 1: if self.dataReady("inbox"): data = self.recv("inbox") self.send(data,"outbox") if self.dataReady("control"): data = self.recv("control") return yield 1 SimpleServer(protocol=EchoProtocol).activate() scheduler.run.runThreads(slowmo=0) The two styles are provided for those comfortable with generators and those who aren't. The plain generator form can be particularly useful in simplifying error handling (see Kamaelia.Internet.TCPClient for an example). The callback form is useful for implementing components in other languages - eg pyrex. Requirements ============ * Python 2.3 or higher recommended, though please report any bugs with 2.2. * Axon (Any released version, 1.0.3 recommended, 1.0.4 when released) * vorbissimple (if you want to use the vorbis decode component) (Both Axon and vorbissimple are separate parts of the Kamaelia project, and available at the same download location - see below) Platforms ========= Kamaelia has been used successfully under both Linux and Windows (2000 and ME). (This has not yet been tested with Axon running on series 60 mobiles since to the select module hasn't been released for Series 60 mobiles yet) Where can I get it? =================== Web pages are here: http://kamaelia.sourceforge.net/Docs/ http://kamaelia.sourceforge.net/ (includes info on mailing lists) ViewCVS access is available here: http://cvs.sourceforge.net/viewcvs.py/kamaelia/ Licensing ========= Kamaelia is released under the Mozilla tri-license scheme (MPL/ GPL/ LGPL). Specifically you may choose to accept either the Mozilla Public License 1.1, the GNU General Public License 2.0 or the Lesser General Public License 2.1. Proprietary terms and conditions available upon request. Best Regards, Michael. -- Michael Sparks, Senior R&D Engineer, Digital Media Group Michael.Sparks(a)rd.bbc.co.uk British Broadcasting Corporation, Research and Development Kingswood Warren, Surrey KT20 6NP This message (and any attachments) may contain personal views which are not the views of the BBC unless specifically stated.

1 0

Online Programming Contest (Python solutions accepted)
by Sridhar R March 2, 2005

March 2, 2005

Hi, We, the students of CEG, Anna University [1] are organizing an online programming contest as part of aBaCus [2] 2005. The contest itself will start on 6th March 2005 at 1:00 pm IST [3] and will end after 5 hours. You have to solve the problems posted at the start of the contest. Teams ranking high will be awarded the prizes. As a special note, inspite of C,C++ and Java we also allow Python [4] this time. So we hope a lot of Pythonistas also could attend the contest for fun. :-) For more details about the contest, visit the contest page -- http://203.197.138.181/OPC -- [1] http://en.wikipedia.org/wiki/Anna_University [2] http://www.annauniv.edu/abacus/ [3] Indian Standard Time (IST) is the time zone for India. It is 5 hours and 30 minutes ahead of GMT/UTC. [4] http://www.python.org -- Sridhar Ratna - http://srid.bsdnerds.org

1 0

[ANN] IPython 0.6.12 is out.
by Fernando Perez March 2, 2005

March 2, 2005

Hi all, I'm glad to announce the release of IPython 0.6.12. This is mainly a bugfix release. IPython's homepage is at: http://ipython.scipy.org and downloads are at: http://ipython.scipy.org/dist I've provided RPMs (for Python 2.3 and 2.4, built under Fedora Core 3), plus source downloads (.tar.gz). We now also have a native win32 installer which should work correctly for both Python 2.3 and 2.4. Debian, Fink and BSD packages for this version should be coming soon, as the respective maintainers (many thanks to Jack Moffit, Andrea Riciputi and Dryice Liu) have the time to follow their packaging procedures. Many thanks to Enthought for their continued hosting support for IPython, and to all the users who contributed ideas, fixes and reports. WHAT is IPython? ---------------- 1. An interactive shell superior to Python's default. IPython has many features for object introspection, system shell access, and its own special command system for adding functionality when working interactively. 2. An embeddable, ready to use interpreter for your own programs. IPython can be started with a single call from inside another program, providing access to the current namespace. 3. A flexible framework which can be used as the base environment for other systems with Python as the underlying language. Release notes ------------- As always, the NEWS file can be found at http://ipython.scipy.org/NEWS, and the full ChangeLog at http://ipython.scipy.org/ChangeLog. * New hooks system. This can be considered the first step in cleaning up ipython to expose its internals in a more rational manner. IPython/hooks.py contains the hooks which are meant to be easily overridden by users for customizations. Currently only the editor hook (called by %edit) exists, but a framework is in place. * Fix a subtle bug with corrupted init files under win32, thanks to Ville Vainio for trackign this. * Fix for Debian, which recently removed the profiler module from the default python distribution and moved it to non-free. * Allow empty and left-aligned output prompts, if users so want them. * New %time magic to time statements and expressions. It reports CPU and wall clock time. * Other small fixes and cleanups. Enjoy, and as usual please report any problems. Regards, Fernando.

1 0

Dr. Dobb's Python-URL! - weekly Python news and links (Mar 1)
by Cameron Laird March 1, 2005

March 1, 2005

Editor's note: "Python-URL!" is minimal. It doesn't support advertisements, we never allow the subscribers' addresses to be used for other purposes, we don't claim infallibility, and we even take a couple weeks off some years. Occasionally, though--not as often as the US enters a shooting war, say, but more frequently than IBM hires a new CEO--we pause for a sufficiently important correction or announcement. This year, we apologize for inexplicably changing Oliver Schoenborn's name a couple of weeks ago to "Philip". Also, has anyone indexed Python bloggers (that is, webloggers of things Pythonic)? QOTW: "... more like generator included." -- Efrat Regev, on the proper characterization of our language of choice VOTW: Steves break ground on VOTWs. Notice the surrounding serious discussions on what exactly makes for an improvement in the language. http://groups-beta.google.com/group/comp.lang.python/msg/1c39adfc9408e225 http://groups-beta.google.com/group/comp.lang.python/msg/1fb3718aee61e4a7 Andrew Kuchling's explanation of PyZeroconf is exemplary: http://www.amk.ca/python/zeroconf All those calendrical/temporal things you need that the standard datetime module doesn't supply? Gustavo Niemeyer supplies (most of) them: https://moin.conectiva.com.br/DateUtil Laugh? Cry? Appeal to the UN? Not only can Python define "(almost) arbitrary infix operators", but you can parametrize their production, with "probably the best Python hack *ever*": http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/384122 Python 3000 might be real, and relatively free of trauma: http://mail.python.org/pipermail/python-dev/2005-January/051363.html Graybeard Steve Holden rambles through the sort of speech that commentators usually take as a sign of breakdown. In this case, though, the delivery has the virtues of: accuracy; and relevance: http://groups-beta.google.com/group/comp.lang.python/msg/9eb125ba50863d57 The state of the art of use of decorations continues to advance: http://groups-beta.google.com/group/comp.lang.python/browse_thread/thread/1… Pythoneers, too, can solve polynomials (although probably not without obscure astronomical, linguistic, artistic, ... references): 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. del.icio.us presents an intriguing approach to reference commentary. It already aggregates quite a bit of Python intelligence. http://del.icio.us/tag/python *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/ (requires subscription) http://groups-beta.google.com/groups?q=python-url+group:comp.lang.python*&s… 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

Vancouver Python User Group Reminder
by Paul Prescod March 1, 2005

March 1, 2005

Tuesday March 1st is the first Tuesday of the month and the Vancouver Python, Zope and Plone user's group will have its monthly meeting at ActiveState (580 Granville) at 7:00. The topic is GNU Radio and Python. GNU Radio is a free software implementation of Software Defined Radio. "Imagine if the only thing stopping your handheld PDA from simultaneously being a GPS receiver, phone, radio or miniature TV was your willingness to download and install some free software program." "We're pretty much turning all hardware problems into software problems," Blossom says. "We want to facilitate evolution in the radio arena." "A software radio is a radio whose channel modulation waveforms are defined in software. That is, waveforms are generated as sampled digital signals, converted from digital to analog via a wideband DAC and then possibly upconverted from IF to RF. The receiver, similarly, employs a wideband Analog to Digital Converter (ADC) that captures all of the channels of the software radio node. The receiver then extracts, downconverts and demodulates the channel waveform using software on a general purpose processor." GNU Radio is a hybrid C++ / Python system. The primitive signal processing blocks are implemented in C++. All graph construction, policy decisions and non-performance critical operations are performed in Python. All of the underlying runtime system is manipulatable from Python. Upcoming talks: April 5, 2005 Large Scale Python

1 0

python-dev Summary for 2005-01-16 through 2005-01-31
by Brett C March 1, 2005

March 1, 2005

===================== Summary Announcements ===================== ----------------------------------------- School sure likes to destroy my free time ----------------------------------------- A month late, that much closer to having this hectic quarter being over. Sorry for being so delinquent with this summary but school has kept me busy and obviously the Real World has to take precedence over volunteer work. Now if I could only get paid for doing this... =) And if you hate the summaries being late, you could do it yourself. This is not meant to be a flippant comment! I am always willing to hand over development of the summaries to anyone who is willing to do a comparable job. If you are interested feel free to email me. I have now made this a permanent offer in the header in case someone comes along later and decides they want to do this. ---------------------- RSS feed now available ---------------------- Thanks entirely to one of my predecessors, A.M. Kuchling, the python-dev Summaries are available as an `RSS feed`_. The feed contains the titles of every summary and so will be updated with the newest summaries as soon as they are posted online. A full text feed will eventually be available. ---------- New format ---------- I have done a thorough restructuring of the boilerplate and the Summary Announcements section for the Summaries. The purpose of this is to make finding information in the boilerplate much easier. It also keeps consistency by sectioning off everything as in the Summary section. The other reason is for the ``contents`` directive in reST_. This will provide a more thorough table of contents for the web version of the summary at the very top of the summaries. This will allow people to jump directly to the section of the Summary they care about the most. Obviously this perk only exists in the HTML version. Lastly, the typical boilerplate for each Summary has now been moved to the bottom. This was at the request of a regular reader who I would like to keep happy. =) It also seems reasonable since once you have read through it once chances are you are not going to read it again so might as well move it out of the way. Then again I could be totally wrong about all of this and manage to alienate every person who reads the summaries regularly. =) ======= Summary ======= --------------------- Python 2.3.5 released --------------------- Consider how late this summary is I bet you already knew Python 2.3.5 was already out the door. =) With Python 2.4 out in the world this means there is a very high probability 2.3.6 will never exist and this marks the end of the 2.3 branch. Contributing threads: - `2.3.5 delayed til next week <http://mail.python.org/pipermail/python-dev/2005-January/051140.html>`__ - `2.3 BRANCH FREEZE imminent! <http://mail.python.org/pipermail/python-dev/2005-January/051277.html>`__ - `RELEASED Python 2.3.5, release candidate 1 <http://mail.python.org/pipermail/python-dev/2005-January/051304.html>`__ ------------------------------------------------------ Making magic type conversion methods act like __str__ ------------------------------------------------------ Walter Dörwald discovered that when you subclass 'unicode' and call unicode() on an instance of the subclass it will not call the implementation of __unicode__ of the subclass but instead will call unicode.__unicode__ . When in the same scenario with strings, though, str() calls the subclass' __str__ method. Turns out 'int' and 'float' act like 'unicode' while 'complex' acts like 'str'. So who is right? Docs say 'str' is wrong, but this is mainly an artifact of pre-2.2 inability to subclass types. Turns out 'str' is acting properly. `Patch #1109424`_ implements the proper semantics and will eventually go in for 2.5 (won't touch 2.4 since it is a semantic change). .. _Patch #1109424: http://www.python.org/sf/1109424 Contributing threads: - `__str__ vs. __unicode__ <http://mail.python.org/pipermail/python-dev/2005-January/051175.html>`__ --------------------------------------------- Speeding up function calls to C API functions --------------------------------------------- Neal Norwitz posted the patch found at http://www.python.org/sf/1107887 to help with function calls to C code. The idea is to expand the family of values used in PyMethodDef.ml_flags for argument types to include specifying the number of minimum and maximum number of arguments. This can provide a speedup by allowing the eval loop to unpack everything in the C stack and skip packing arguments in a tuple. But not everyone was sure it was worth the extra need to specify all of this for functions. Regardless of that and any other objections this would be more of a Python 3000 thing. Which also led to a quick shift in topic to how Python 3.0 will be developed. Guido said it would be piece-meal. Read http://joelonsoftware.com/articles/fog0000000069.html for why. Contributing threads: - `Speed up function calls <http://mail.python.org/pipermail/python-dev/2005-January/051251.html>`__ - `Moving towards Python 3.0 <http://mail.python.org/pipermail/python-dev/2005-January/051355.html>`__ ------------------------------------------------------------ How to handle memory allocation with the presence of threads ------------------------------------------------------------ Evan Jones has been working on a patch to allow the garbage collector to free up memory of small objects. This led him to ask questions in terms of memory usage in the face of threading at the C level. While the GIL usually needs to be held for any operation that touches Python code, he was not sure if this held for the memory API. Tim Peters clarified all of this by pointing out the documentation in the C API manual about the GIL. In a nutshell the memory API is not exempt from needing to hold the GIL, so hold it. It was also pointed out there was a bunch of code to allow people to mix usage of PyMem_* functions with PyObject_* functions. That was purely done for backwards-compatibility back in the day. Mixing these two APIs for memory is very bad. Don't do it! Contributing threads: - `Improving the Python Memory Allocator <http://mail.python.org/pipermail/python-dev/2005-January/051255.html>`__ - `Python Interpreter Thread Safety? <http://mail.python.org/pipermail/python-dev/2005-January/051335.html>`__ -------------------------- Slicing iterators rejected -------------------------- Nick Coghlan proposed allowing iterators to be sliced liked other sequence types. That way something like ``enumerate("ABCD")[1:]`` would work. But Guido rejected it. With itertools.islice existence it does not provide new functionality. Plus "Iterators are for single sequential access" according to Guido, and thus should not be confused with sequences. Contributing threads: - `Allowing slicing of iterators <http://mail.python.org/pipermail/python-dev/2005-January/051257.html>`__ =============== Skipped Threads =============== - redux: fractional seconds in strptime - how to test behavior wrt an extension type? - Strange segfault in Python threads and linux kernel 2.6 - Unix line endings required for PyRun* breaking embedded Python - Zen of Python - PyCon: The Spam Continues ;-) - Patch review: [ 1094542 ] add Bunch type to collections module ======== Epilogue ======== ------------ Introduction ------------ This is a summary of traffic on the `python-dev mailing list`_ from January 16, 2005 through January 31, 2005. It is intended to inform the wider Python community of on-going developments on the list on a semi-monthly basis. An archive_ of previous summaries is available online. An `RSS feed`_ of the titles of the summaries is available. You can also watch comp.lang.python or comp.lang.python.announce for new summaries (or through their email gateways of python-list or python-announce, respectively, as found at http://mail.python.org). This is the fifty-seventh summary written by Brett Cannon (grad schools are actually crazy enough to accept me =). To contact me, please send email to brett at python.org. Do *not* post to comp.lang.python if you wish to reach me. The `Python Software Foundation`_ is the non-profit organization that holds the intellectual property for Python. It also tries to advance the development and use of Python. If you find the python-dev Summary helpful please consider making a donation. You can make a donation at http://python.org/psf/donations.html . Every penny helps so even a small donation with a credit card, check, or by PayPal helps. If you are looking for a way to expand your knowledge of Python's development and inner-workings, consider writing the python-dev Summaries yourself! I am willing to hand over the reins to someone who is willing to do a comparable or better job of writing the Summaries. If you are interested, please email me at brett at python.org. -------------------- Commenting on Topics -------------------- 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`_! ------------------------- How to Read the Summaries ------------------------- 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 for 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. Please note that this summary is written using reStructuredText_. Any unfamiliar punctuation is probably markup for reST_ (otherwise it is probably regular expression syntax or a typo =); you can safely ignore it. I do suggest learning reST, though; it's simple and is accepted for `PEP markup`_ and can be turned into many different formats like HTML and LaTeX. Unfortunately, even though reST is standardized, the wonders of programs that like to reformat text do not allow me to 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`_. .. _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 .. _PEP Markup: http://www.python.org/peps/pep-0012.html .. _Docutils: http://docutils.sf.net/ .. _reST: .. _reStructuredText: http://docutils.sf.net/rst.html .. _PSF: .. _Python Software Foundation: http://python.org/psf/ .. _last summary: http://www.python.org/dev/summary/2005-01-01_2005-01-15.html .. _original text file: http://www.python.org/dev/summary/2005-01-16_2005-01-31.ht .. _archive: http://www.python.org/dev/summary/ .. _RSS feed: http://www.python.org/dev/summary/channews.rdf

1 0

[ANN] pyasm 0.1 - x86 assembler for Python
by Grant Olson March 1, 2005

March 1, 2005

pyasm 0.1 - x86 assembler for Python This release is for early adopters only. It is not properly packaged and doesn't have very good documentation. It is however a functional assembler that should be of interest to some people. Current output targets include Windows-style COFF files that can be subsequently linked to produce executables, and more interestingly output can target memory in an existing Python process and binding within a Python namespace. That's right, you can now generate dynamic inline assembly straight from Python! A simple hello world function implementation is listed at the end of this message. The files test\test_object_creation.py and test\test_winmem.py in the distribution probably give the best examples of usage. Future plans include targeting ELF file formats and Linux memory at runtime, and of course real documentation. The package is available at: http://mysite.verizon.net/olsongt/pyasm-0.1.zip Enjoy, -Grant ############################################# # PYTHON HELLO WORLD IN ASSEMBLY ############################################# import pyasm.winmem from pyasm.x86asm import assembler, CDECL from pyasm.x86cpToMemory import CpToMemory nonePointer = id(None) a = assembler() a.ADStr("hello_world", "Hello world!\n\0") a.AP("test_print", CDECL) a.AddLocal("self") a.AddLocal("args") #a.AI("INT 3") a.AI("PUSH hello_world") a.AI("CALL PySys_WriteStdout") #a.AI("INT 3") a.AI("MOV EAX,%s" % id(None)) a.AI("ADD [EAX],0x1") #refcount manipulation a.EP() mem = CpToMemory(a.Compile(),pyasm.winmem) mem.MakeMemory() mem.BindPythonFunctions(globals()) test_print() # calls the assembly function

1 0