Mailman 3 November 2005 - Python-announce-list

Fredericksburg VA ZPUG: No December meeting; details on Jan and Feb meetings
by Gary Poster Nov. 27, 2005

Nov. 27, 2005

As discussed at the November Fredericksburg, VA ZPUG meeting, we are not going to have a December 14 ZPUG because of holiday goings-on. Andrew Sawyers will present on Squid and Zope in our January 11 meeting (other topics TBD). Zac Bir, Benji York, and Gary Poster will present in our February 8 meeting in an all-Twisted session based very loosely on the new O'Reilly Twisted book (http://www.oreilly.com/catalog/twistedadn/ index.html), with Zac concentrating on Twisted and OS X, Gary concentrating on Twisted and Zope 3, and Benji giving a lightning talk of his impressions of the book. General ZPUG information When: second Wednesday of every month, 7:30-9:00 (except not December 14, 2005!) Where: Zope Corporation offices. 513 Prince Edward Street; Fredericksburg, VA 22408 (tinyurl for map is http://tinyurl.com/duoab). Parking: Zope Corporation parking lot; entrance on Prince Edward Street. Topics: As desired (and offered) by participants, within the constraints of having to do with Python or Zope. Contact: Gary Poster (gary(a)zope.com)

1 0

python-dev Summary for 2005-11-01 through 2005-11-15
by Tony Meyer Nov. 27, 2005

Nov. 27, 2005

[The HTML version of this Summary will be available at http://www.python.org/dev/summary/2005-11-01_2005-11-15.html] ============= Announcements ============= ---------------------------------------- PyPy 0.8.0 and Gothenburg PyPy Sprint II ---------------------------------------- `PyPy 0.8.0`_ has been released. This third release of PyPy includes a translatable parser and AST compiler, some speed enhancements (transated PyPy is now about 10 times faster than 0.7, but still 10-20 times slower than CPython), increased language compliancy, and some experimental features are now translatable. This release also includes snapshots of interesting, but not yet completed, subprojects including the OOtyper (a RTyper variation for higher-level backends), a JavaScript backend, a limited (PPC) assembler backend, and some bits for a socket module. The next PyPy Sprint is also coming up soon. The Gothenborg PyPy Sprint II is on the 7th to 11th of December 2005 in Gothenborg, Sweden. Its focus is heading towards phase 2, which means JIT work, alternate threading modules, and logic programming. Newcomer-friendly introductions will also be given. The main topics that are currently scheduled are the L3 interpreter (a small fast interpreter for "assembler-level" flow graphs), Stackless (e.g. Tasklets or Greenlets), porting C modules from CPython, optimization/debugging work, and logic programming in Python. .. _`PyPy 0.8.0`: http://codespeak.net/pypy/dist/pypy/doc/release-0.8.0.html Contributing threads: - `PyPy 0.8.0 is released! < http://mail.python.org/pipermail/python-dev/2005-November/057878.html>`__ - `Gothenburg PyPy Sprint II: 7th - 11th December 2005 < http://mail.python.org/pipermail/python-dev/2005-November/058143.html>`__ [TAM] ------------------------ PyCon Sprint suggestions ------------------------ Every PyCon has featured a python-dev `sprint`_. For the past few years, hacking on the AST branch has been a tradition, but since the AST branch has now been merged into the trunk, other options are worth considering this year. Several PEP implementations were suggested, including `PEP 343`_ ('with:'), `PEP 308`_ ('x if y else z'), `PEP 328`_ ('absolute/relative import'), and `PEP 341`_ ('unifying try/except and try/finally'). Suggestions to continue the AST theme were also made, including one of the "global variable speedup" PEPs, `Guido's instance variable speedup idea`_, using the new AST code to improve/extend/rewrite the optimization steps the compiler performs, or rewriting PyChecker to operate from the AST representation. Phillip J. Eby also suggested working on the oft-mentioned bytes type. All of these suggestions, as well as any others that are made, are being recorded on the `PythonCore sprint wiki`_. .. _sprint: http://wiki.python.org/moin/PyCon2006/Sprints .. _PEP 343: http://www.python.org/peps/pep-0343.html .. _PEP 308: http://www.python.org/peps/pep-0308.html .. _PEP 328: http://www.python.org/peps/pep-0328.html .. _PEP 341: http://www.python.org/peps/pep-0341.html .. _Guido's instance variable speedup idea: http://mail.python.org/pipermail/python-dev/2002-February/019854.html .. _PythonCore sprint wiki: http://wiki.python.org/moin/PyCon2006/Sprints/PythonCore Contributing threads: - `python-dev sprint at PyCon < http://mail.python.org/pipermail/python-dev/2005-November/057830.html>`__ - `PEP 328 - absolute imports (python-dev sprint at PyCon) < http://mail.python.org/pipermail/python-dev/2005-November/057853.html>`__ [TAM] -------------------------------------- Reminder: Python is now on Subversion! -------------------------------------- Just a reminder to everyone that the Python source repository_ is now hosted on Subversion. A few minor bugs were fixed, so you can make SVK mirrors of the repository successfully now. Be sure to check out the newly revised Python Developers FAQ_ if you haven't already. .. _repository: http://svn.python.org/projects/ .. _FAQ: http://www.python.org/dev/devfaq.html Contributing threads: - `Freezing the CVS on Oct 26 for SVN switchover < http://mail.python.org/pipermail/python-dev/2005-November/057823.html>`__ - `svn checksum error < http://mail.python.org/pipermail/python-dev/2005-November/057843.html>`__ - `Problems with revision 4077 of new SVN repository < http://mail.python.org/pipermail/python-dev/2005-November/057867.html>`__ - `No more problems with new SVN repository < http://mail.python.org/pipermail/python-dev/2005-November/057888.html>`__ - `dev FAQ updated with day-to-day svn questions < http://mail.python.org/pipermail/python-dev/2005-November/057999.html>`__ - `Mapping cvs version numbers to svn revisions? < http://mail.python.org/pipermail/python-dev/2005-November/058051.html>`__ - `Checking working copy consistency < http://mail.python.org/pipermail/python-dev/2005-November/058056.html>`__ - `Is some magic required to check out new files from svn? < http://mail.python.org/pipermail/python-dev/2005-November/058065.html>`__ [SJB] --------------------------- Updating the Python-Dev FAQ --------------------------- Brett Cannon has generously volunteered to clean up some of the developers' documentation and wants to know if people would rather the bug/patch guidelines to be in a classic paragraph-style layout or a more FAQ-style layout. If you have an opinion on the topic, please let him know! Contributing threads: - `dev FAQ updated with day-to-day svn questions < http://mail.python.org/pipermail/python-dev/2005-November/058025.html>`__ - `Revamping the bug/patch guidelines (was Re: Implementation of PEP 341) < http://mail.python.org/pipermail/python-dev/2005-November/058108.html>`__ [SJB] ========= Summaries ========= ----------- Event loops ----------- This thread initiated in discussion on sourceforge about patches 1049855_ and 1252236_; Martin v. Löwis and Michiel de Hoon agreed that the fixes were fragile, and that a larger change should be discussed on python-dev. Michiel writes visualization software; he (and others, such as the writers of matplotlib) has trouble creating a good event loop, because the GUI toolkit (especially Tkinter) wants its own event loop to be in charge. Michiel doesn't actually need Tkinter for his own project, but he has to play nice with it because his users expect to be able to use other tools -- particularly IDLE -- while running his software. Note that this isn't the first time this sort of problem has come up; usually it is phrased in terms of a problem with Tix, or not being able to run turtle while in IDLE. Event loops by their very nature are infinite loops; once they start, everything else is out of luck unless it gets triggered by an event or is already started. Donovan Baarda suggested looking at Twisted for state of the art in event loop integration. Unfortunately, as Phillip Eby notes, it works by not using the Tkinter event loop. It decides for itself when to call dooneevent (do-one-event). It is possible to run Tkinter's dooneevent version as part of your own event loop (as Twisted does), but you can't really listen for its events, so you end up with a busy loop polling, and stepping into lots of "I have nothing to do" functions for every client eventloop. You can use Tkinter's loop, but once it goes to sleep waiting for input, everything sort of stalls out for a while, and even non-Tkinter events get queued instead of processed. Mark Hammond suggests that it might be easier to replace the interactive portions of python based on the "code" module. matplotlib suggests using ipython instead of standard python for similar reasons. Another option might be to always start Tk in a new thread, rather than letting it take over the main thread. There was some concern (see patch 1049855) that Tkinter doesn't - and shouldn't - require threading. [Jim Jewett posted a summary of this very repetitive and confusing (to the participants, not just summarizers!) thread towards its end, which this summary is very heavily based on. Many thanks Jim!] Contributing threads: - `Event loops, PyOS_InputHook, and Tkinter < http://mail.python.org/pipermail/python-dev/2005-November/057954.html>`__ - `Event loops, PyOS_InputHook, and Tkinter - Summary attempt < http://mail.python.org/pipermail/python-dev/2005-November/058034.html>`__ .. _1049855: http://www.python.org/sf/1049855 .. _1252236: http://www.python.org/sf/1252236 [TAM] ----------------------------- Importing .pyc and .pyo files ----------------------------- Osvaldo Santana Neto pointed out that if a .pyo file exists, but a .pyc doesn't, then a regularly run python will not import it (unless run with -O), but if the .pyo is in a zip file (which is on the PYTHONPATH) then it will import it. He felt that the inconsistency should be addressed and that the zipimport behaviour was preferable. However, Guido said that his intention was always that, without -O, *.pyo files are entirely ignored (and, with -O, *.pyc files are entirely ignored). In other words, it is the zipimport behaviour that is incorrect. Guido suggested that perhaps .pyo should be deprecated altogether and instead we could have a post-load optimizer optimize .pyc files according to the current optimization settings. The two use cases presented for including .pyo files but not .py files were in situations where disk space is at a premium, and where a proprietary "canned" application is distributed to end users who have no intention or need to ever add to the code. A suggestion was that a new bytecode could be introduced for assertions that would turn into a jump if assertions were disabled (with -O). Guido thought that the idea had potential, but pointed out that it would take someone thinking really hard about all the use cases, edge cases, implementation details, and so on, in order to write a PEP. He suggested that Brett and Phillip might be suitable volunteers for this. Contributing thread: - `Inconsistent behaviour in import/zipimport hooks < http://mail.python.org/pipermail/python-dev/2005-November/057959.html>`__ [TAM] --------------------------------------- Default __hash__() and __eq__() methods --------------------------------------- Noam Raphael suggested that having the default __hash__() and __eq__() methods based off of the object's id() might have been a mistake. He proposed that the default __hash__() method be removed, and the default __eq__() method compare the two objects' __dict__ and slot members. Jim Fulton offered a counter-proposal that both the default __hash__() and __eq__() methods should be dropped for Python 3.0, but Guido convinced him that removing __eq__() is probably a bad idea; it would mean an object wouldn't compare equal to itself. In the end, Guido decided that having a default __hash__() method based on id() isn't really a bad decision; without it, you couldn't have sets of "identity objects" (objects which don't have a usefully defined value-based comparison). He suggested that the right decision was to make the hash() function smarter, and have it raise an exception if a class redefined __eq__() without redefining __hash__(). (In fact, this is what it used to do, but it was lost when object.__hash__() was introduced.) Contributing threads: - `Why should the default hash(x) == id(x)? < http://mail.python.org/pipermail/python-dev/2005-November/057859.html>`__ - `Should the default equality operator compare values instead of identities? < http://mail.python.org/pipermail/python-dev/2005-November/057868.html>`__ - `For Python 3k, drop default/implicit hash, and comparison < http://mail.python.org/pipermail/python-dev/2005-November/057924.html>`__ [SJB] --------------------------- Indented multi-line strings --------------------------- Avi Kivity reintroduced the oft-requested means of writing a multi-line string without getting the spaces from the code indentation. The usual options were presented:: def f(...): ... msg = ('From: %s\n' 'To: %s\n' 'Subject: Host failure report for %s\n') ... msg = '''\ From: %s To: %s Subject: Host failure report for %s''' ... msg = textwrap.dedent('''\ From: %s To: %s Subject: Host failure report for %s''') Noam Raphael suggested that to simplify the latter option, textwrap.dedent() should become a string method, str.dedent(). There were also a few suggestions that this sort of dedenting should have syntactic support (e.g. with an appropriate string prefix). In general, the discussion harkened back to `PEP 295`_, a similar proposal that was previously rejected. People tossed the ideas around for a bit, but it didn't look like any changes were likely to be made. .. _PEP 295: http://www.python.org/peps/pep-0295.html Contributing threads: - `indented longstrings? < http://mail.python.org/pipermail/python-dev/2005-November/058042.html>`__ - `str.dedent < http://mail.python.org/pipermail/python-dev/2005-November/058058.html>`__ - `OT pet peeve (was: Re: str.dedent) < http://mail.python.org/pipermail/python-dev/2005-November/058072.html>`__ [SJB] ------------------ Continued AST work ------------------ Neal Norwitz has been chasing down memory leaks; he believes that the current AST is now as good as before the AST branch was merged in. Nick explained that he is particularly concerned about the returns hidden inside in macros in the AST compiler's symbol table generation and bytecode generation steps. Niko Matsakis suggested that an arena is the way to go for memory management; the goal is to be able to free memory en-masse whatever happens and not have to track individual pointers. Jeremy Hylton noted that the AST phase has a mixture of malloc/free and Python object allocation; he felt that it should be straightforward to change the malloc/free to use an arena API, but that a separate mechanism would be needed to associate a set of PyObject* with the arena. The arena concept gained general approval, and there was some discussion about how best to implement it. In other AST news Rune Holm submitted two_ patches_ for the AST compiler that add better dead code elimination and constant folding and Thomas Lee is attempting to implement `PEP 341`_ (unification of try/except and try/finally), and asked for some help (Nick Coghlan gave some suggestions). .. _two: http://www.python.org/sf/1346214 .. _patches: http://www.python.org/sf/1346238 .. _PEP 341: http://python.org/peps/pep-0341.html Contributing threads: - `Optimizations on the AST representation < http://mail.python.org/pipermail/python-dev/2005-November/057865.html>`__ - `Implementation of PEP 341 < http://mail.python.org/pipermail/python-dev/2005-November/058075.html>`__ - `ast status, memory leaks, etc < http://mail.python.org/pipermail/python-dev/2005-November/058089.html>`__ - `Memory management in the AST parser & compiler < http://mail.python.org/pipermail/python-dev/2005-November/058138.html>`__ - `PEP 341 patch & memory management (was: Memory management in the AST parser & compiler) < http://mail.python.org/pipermail/python-dev/2005-November/058142.html>`__ [TAM] --------------------------------------------------------------------- Adding functional methods (reduce, partial, etc.) to function objects --------------------------------------------------------------------- Raymond Hettinger suggested that some of the functionals, like map or partial, might be appropriate as attributes of function objects. This would allow code like:: results = f.map(data) newf = f.partial(somearg) A number of people liked the idea, but it was pointed out that map() and partial() are intended to work with any callable, and turning these into attributes of function objects would make it hard to use them with classes that define __call__(). Guido emphasized this point, saying that complicating the callable interface was a bad idea. Contributing thread: - `a different kind of reduce... < http://mail.python.org/pipermail/python-dev/2005-November/057828.html>`__ [SJB] -------------------------------------------------- Distributing debug build binaries (python2x_d.dll) -------------------------------------------------- David Abrahams asked whether it would be possible for python.org to make a debug build of the Python DLL more accessible. Thomas Heller pointed out that the Microsoft debug runtime DLLs are not distributable (which is why the Windows installer does not include the debug version of the Python DLL), and that the ActiveState distribution contains Python debug DLLs. Tim Peters explained that when he used to collect up the debug-build bits at the time the official installer was built, they weren't included in the main installer, because they bloated its size for something that most users don't want. He explained that he stopped collecting the bits because no two users wanted the same set of stuff, and so it grew so large that people complained that it was too big. Tim suggested that the best thing to do would be to define precisely what an acceptable distribution format is and what exactly it should contain. Martin indicated that he would accept a patch that picked up the files and packages them, and he would include them in the official distribution. Contributing thread: - `Plea to distribute debugging lib < http://mail.python.org/pipermail/python-dev/2005-November/057896.html>`__ [TAM] ----------------------------------- Creating a python-dev-announce list ----------------------------------- Jack Jansen suggested that a low-volume, moderated, python-dev-announce mailing list be created for time-critical announcements for people developing Python. The main benefit would be the ability to keep up with important announcements such as new releases, the switch to svn, and so on, even when developers don't have time to keep up with all threads. Additionally, it would be easier to separate out such announcements, even when following all threads. Although these summaries exist (and the announcements section at the top pretty much covers what Jack is after), the summaries occur at least a week after the end of the period that they cover, which could be as much as three weeks after any announcement (if it occurred on the first of a month, for example). I suggested that a simpler possibility might follow along the lines of the PEP topic that the python-checkins list provides (a feature of Mailman). This would still require some sort of effort by the announcer (e.g. putting some sort of tag in the subject), but wouldn't require an additional list, or additional moderators. However, Martin pointed out that this would put an extra burden on people to remember to post to such a list; this burden would also exist using the Mailman topic mechanism. There wasn't much apparent support for the list, so this seems unlikely to occur at present. Of course, that could be because the people that would like it are too busy to have noticed the thread yet <0.5 wink>, so perhaps there is more to come. Contributing thread: - `Proposal: can we have a python-dev-announce mailing list? < http://mail.python.org/pipermail/python-dev/2005-November/057880.html>`__ [TAM] ------------------------------------- Notifications of weakref dereferences ------------------------------------- When integrating with another system (such as gtk), it can be useful if each object in the other system maps to (at most) one python wrapper. If python references drop to zero, then the next python reference would (by default) create a different wrapper object. So the wrapper tries to stay alive (with only a weak reference to the true object) as long as the true object does. But if that wrapper does get used, it needs to replace the weak reference with a strong reference. The standard weakref callbacks weren't quite up to the task, but it looked like there were workarounds, either by abusing weakref methods in a subtask, or by changing the architecture slightly. Contributing thread: - `Weak references: dereference notification < http://mail.python.org/pipermail/python-dev/2005-November/057961.html>`__ [Jim Jewett] -------------------------------------------- Should 1.2 be a floating point or a decimal? -------------------------------------------- There was general agreement that decimal might deserve a literal marker of its own in python 3.0, but much less agreement that it should be the default floating or fixed point representation. Decimals are better for many business applications, but floats are faster and are better for most scientific and engineering applications. Contributing thread: - `Unifying decimal numbers. < http://mail.python.org/pipermail/python-dev/2005-November/057951.html>`__ [Jim Jewett] ----------------------- Speeding up int(string) ----------------------- Uncle Timmy wants python to do better on certain benchmarks, and gave `an example`_. The bottleneck turns out to be parsing an integer from a string. At the moment, this is not only slow, it has potential bugs. Patches were submitted, but had not been applied at the time this summary was written. .. _an example: http://spoj.sphere.pl/ Contributing threads: - `int(string) (was: DRAFT: python-dev Summary for 2005-09-01 through 2005-09-16) < http://mail.python.org/pipermail/python-dev/2005-November/057994.html>`__ - `to_int -- oops, one step missing for use. < http://mail.python.org/pipermail/python-dev/2005-November/058006.html>`__ - `(no subject) < http://mail.python.org/pipermail/python-dev/2005-November/058023.html>`__ [Jim Jewett] ---------------------------------------------------- Building Python with Visual C++ 2005 Express Edition ---------------------------------------------------- Is it possible? Probably, but like other newer VC++ there are problems, particularly with changes to crt, and deprecation of standard interfaces. It won't become the "standard" build tool. Contributing thread: - `Building Python with Visual C++ 2005 Express Edition < http://mail.python.org/pipermail/python-dev/2005-November/058024.html>`__ [Jim Jewett] ------------------------ Freezing mutable objects ------------------------ `Last fortnight's thread` about ways to take an immutable snapshot of an otherwise mutable object continued. Discussions centered around how true the reflection has to be, and how to do this efficiently; an agreement was difficult to come to. Contributing thread: - `apparent ruminations on mutable immutables (was: PEP 351, the freeze protocol) < http://mail.python.org/pipermail/python-dev/2005-November/057839.html>`__ .. _Last fortnight's thread: http://www.python.org/dev/summary/2005-10-16_2005-10-31.html#freeze-protocol [TAM] =============== Skipped Threads =============== - `Divorcing str and unicode (no more implicit conversions). < http://mail.python.org/pipermail/python-dev/2005-November/057827.html>`__ - `[C++-sig] GCC version compatibility < http://mail.python.org/pipermail/python-dev/2005-November/057831.html>`__ - `PYTHOPN_API_VERSION < http://mail.python.org/pipermail/python-dev/2005-November/057879.html>`__ - `Adding examples to PEP 263 < http://mail.python.org/pipermail/python-dev/2005-November/057891.html>`__ - `Class decorators vs metaclasses < http://mail.python.org/pipermail/python-dev/2005-November/057904.html>`__ - `PEP 352 Transition Plan < http://mail.python.org/pipermail/python-dev/2005-November/057911.html>`__ - `PEP submission broken? < http://mail.python.org/pipermail/python-dev/2005-November/057935.html>`__ - `cross-compiling < http://mail.python.org/pipermail/python-dev/2005-November/057939.html>`__ - `[OTAnn] Feedback < http://mail.python.org/pipermail/python-dev/2005-November/057941.html>`__ - `Weekly Python Patch/Bug Summary < http://mail.python.org/pipermail/python-dev/2005-November/057949.html>`__ - `Coroutines (PEP 342) < http://mail.python.org/pipermail/python-dev/2005-November/058133.html>`__ ======== Epilogue ======== This is a summary of traffic on the `python-dev mailing list`_ from November 01, 2005 through November 15, 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 7th summary written by the python-dev summary squad of Steve Bethard and Tony Meyer (so nice to be back on time!). To contact us, please send email: - Steve Bethard (steven.bethard at gmail.com) - Tony Meyer (tony.meyer at gmail.com) Do *not* post to comp.lang.python if you wish to reach us. 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. -------------------- 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. We 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 us 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 .. _c.l.py: .. _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-10-01_2005-10-15.html .. _original text file: http://www.python.org/dev/summary/2005-11-01_2005-11-15.ht .. _archive: http://www.python.org/dev/summary/ .. _RSS feed: http://www.python.org/dev/summary/channews.rdf

1 0

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

Nov. 26, 2005

QOTW: "... '[B]ut assume that I have some other use case' isn't a valid use case". - Fredrik Lundh "Rolling your own solution, on the other hand, can end in a long road discovering what those CORBA people were doing for all those years." - Paul Boddie NOTW: sceptifications. Steven D'Aprano carefully details a common confusion among newcomers about empty lists and initialization: http://groups.google.com/group/comp.lang.python/browse_thread/thread/8480fa… Inyeol Lee and others illustrate use of regular expression syntax having to do with repeated patterns: http://groups.google.com/group/comp.lang.python/browse_thread/thread/b5e7ab… Metakit 2.4.9.5 corrects a potential disk-full error, and improves performance greatly in certain circumstances: http://www.equi4.com/pub/mk/CHANGES http://www.equi4.com/metakit.html William Peterson jokes that, "[i]f you ask ten people on this newsgroup [about GUI construction newcomers] you'll probably get twelve opinions"--and then the community promptly proves him right: http://groups.google.com/group/comp.lang.python/browse_thread/thread/6fd1ea… Having arrived in the twenty-first century, clp now has its own (provisional) podcast: http://groups.google.com/group/comp.lang.python/browse_thread/thread/b39581… David Wahler cogently perverts^H^H^H^H^H^H^H^Hextends pickle to serialize *classes* (as opposed to their instances): http://groups.google.com/group/comp.lang.python/browse_thread/thread/10a03f… Fully-general backward-compatibility has substantial costs, often greater than the version migration it's supposed to spare us. Several of the regulars discuss this seriously: http://groups.google.com/group/comp.lang.python/browse_thread/thread/423d9d… __slots__ are only a (memory) optimization, restricted to well-defined circumstances, explains the martellibot: http://groups.google.com/group/comp.lang.python/browse_thread/thread/1cc68d… A good thing about Cheetah is that it cooperates with Python's inheritance: http://groups.google.com/group/comp.lang.python/browse_thread/thread/f06340… ======================================================================== 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. For far, FAR more Python reading than any one mind should absorb, much of it quite interesting, several pages index much of the universe of Pybloggers. http://lowlife.jp/cgi-bin/moin.cgi/PythonProgrammersWeblog http://www.planetpython.org/ http://mechanicalcat.net/pyblagg.html 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 Steve Bethard, Tim Lesher, and Tony Meyer continue the marvelous tradition early borne by Andrew Kuchling, Michael Hudson and Brett Cannon 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/ 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… There is *not* an RSS for "Python-URL!"--at least not yet. Arguments for and against are occasionally entertained. 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

Guppy-PE: A Python Programming Environment
by sverker.is＠home.se Nov. 25, 2005

Nov. 25, 2005

I would like to announce Guppy-PE 0.1 The first version of Guppy-PE, a programming environment providing object and heap memory sizing and analysis and comes with a prototypical specification language that can be used to formally specify aspects of Python programs and generate tests and documentation from a common source. License: MIT For more information, see: http://guppy-pe.sourceforge.net Best Regards, Sverker Nilsson sverker.is(a)home.se

1 0

ANN: Porcupine Web Application Server 0.0.5 released
by t.koutsovassilis＠gmail.com Nov. 23, 2005

Nov. 23, 2005

Sorry for posting this again but the new release is the 0.0.5 and not the 0.0.4. QuiX now supports radio buttons and timers (timeouts and intervals). This release also introduces a couple of useful desktop enhancements. The task bar context menu allows the user to minimize all windows or activate the desired window at once. Each user is also capable of choosing the task bar position (top or bottom). The object query language (POQL) is enriched by adding a new function named "instanceof". This function returns "true" if an object is a subclass of a given type. Finally a new dictionary data type is added to the list of the primary data types and the user content class has a new attribute used for keeping his/her preferences. One step closer to our vision; the WebOS. Resources ========= What is Porcupine? http://www.innoscript.org/content/view/30/42/ Porcupine online demo: http://www.innoscript.org/content/view/21/43/ Porcupine tutorials: http://wiki.innoscript.org/index.php/Developers/Tutorials Developer resources: http://www.innoscript.org/component/option,com_remository/Itemid,33/func,se…

1 0

ANN: PyTables 1.2
by Francesc Altet Nov. 23, 2005

Nov. 23, 2005

PyTables is a library to deal with very large datasets. It leverages the excellent HDF5 and numarray libraries to allow doing that in a very efficient way using the Python language. More info in: http://pytables.sourceforge.net/ ========================= Announcing PyTables 1.2 ========================= The PyTables development team is happy to announce the availability of a new major version of PyTables package. This version sports a completely new in-memory tree implementation based around a *node cache system*. This system loads nodes only when needed and unloads them when they are rarely used. The new feature allows the opening and creation of HDF5 files with large hierarchies very quickly and with a low memory consumption (the object tree is no longer completely loaded in-memory), while retaining all the powerful browsing capabilities of the previous implementation of the object tree. You can read more about the dings and bells of the new cache system in: http://www.carabos.com/downloads/pytables/NewObjectTreeCache.pdf Also, Jeff Whitaker has kindly contributed a new module called tables.NetCDF. It is designed to be used as a drop-in replacement for Scientific.IO.NetCDF, with only minor actions to existing code. Also, if you have the Scientific.IO.NetCDF module installed, it allows to do conversions between HDF5 <--> NetCDF3 formats. Go to the PyTables web site for downloading the beast: http://pytables.sourceforge.net/ If you want more info about this release, please check out the more comprehensive announcement message available in: http://www.carabos.com/downloads/pytables/ANNOUNCE-1.2.html Acknowledgments =============== Thanks to the users who provided feature improvements, patches, bug reports, support and suggestions. See THANKS file in distribution package for a (incomplete) list of contributors. Many thanks also to SourceForge who have helped to make and distribute this package! And last but not least, a big thank you to THG (http://www.hdfgroup.org/) for sponsoring many of the new features recently introduced in PyTables. --- **Enjoy data!** -- The PyTables Team -- >0,0< Francesc Altet http://www.carabos.com/ V V Cárabos Coop. V. Enjoy Data "-"

1 0

ANN: Porcupine Web Application Server 0.0.4 released
by t.koutsovassilis＠gmail.com Nov. 23, 2005

Nov. 23, 2005

QuiX now supports radio buttons and timers (timeouts and intervals). This release also introduces a couple of useful desktop enhancements. The task bar context menu allows the user to minimize all windows or activate the desired window at once. Each user is also capable of choosing the task bar position (top or bottom). The object query language (POQL) is enriched by adding a new function named "instanceof". This function returns "true" if an object is a subclass of a given type. Finally a new dictionary data type is added to the list of the primary data types and the user content class has a new attribute used for keeping his/her preferences. One step closer to our vision; the WebOS. Resources ========= What is Porcupine? http://www.innoscript.org/content/view/30/42/ Porcupine online demo: http://www.innoscript.org/content/view/21/43/ Porcupine tutorials: http://wiki.innoscript.org/index.php/Developers/Tutorials Developer resources: http://www.innoscript.org/component/option,com_remository/Itemid,33/func,se…

1 0

a contest open to various programming languages (including Python)
by Chrys Nov. 22, 2005

Nov. 22, 2005

The second edition of the programming contest TopDev2006 will take place on January 28th-29th 2006. This contest is original by its independance from any languages. The winners will not be the fastest programmer, but the ones who will propose the greatest technical solution with the most complete documentation.("it's not a speed contest, upon an arithmetical problem"). Anyone can contest TopDev (students or professionals, alone or in pair,...). More than thousand of participants are expected for this world-wide contest. A realistic and detailed business case is to be realized using any language (Java, PHP, C#, ASP.Net, Python,...or an UML model) within only 60 hours, from home. Subscription and more informations : http://www.TopDevOne.com

1 0

ANN:NewEdit 3.1 released
by limodou Nov. 22, 2005

Nov. 22, 2005

What's it? ======== It's an Editor based on wxPython. NewEdit uses Mixin and Plugin technique as its architecture. Most of its classes can be extended via mixin and plugin components, and finally become an integrity class at creating the instance. So NewEdit is very dynamic. You can write the new features in new files, and hardly need to modify the existing code. And if you want to extend the existing classes, you could write mixins and plugins, and this will be bound to the target class that I call "Slot Class". This technique will make the changes centralized and easily managed. What are its features? ================ * Cross platform o based on wxPython, so it can run anywhere that wxPython works, such as: Windows, Linux. o Unicode support. * Most features of wxStyledTextCtrl(Scintilla) o Syntax highlighting, support Python, c/c++, html, plain text, perl, ruby, css, javascript o Folding o Brace Matching o ... * Extended selection o Extended word selection -- You can press Ctrl+?MouseDoubleClick to select a word including '.' o Matched selection -- Select text in quoted chars like: (), [], {}, '', "". * Other editing extension o Duplicating text -- Just like Vim Ctrl+V, Ctrl+P, and more. You can duplicate above or below char, word, line o Quoting text -- Add some quoted chars before and after selected text, just as: "", '', (), [], {}, and o Text convertion and view -- python -> html, reStructured Text -> html, textile -> html, and you can output or view o Utf-8 encoding auto detect o Changing document encoding o Auto backup o Last session support -- It'll save all the filenames as closed, and reopen the files as next started. o Smart judge the indent char -- It'll auto guess the indent char, and sets it. o Finding in files o Bookmark support * Python support o built-in python interactive window based on ?PyShell, support Unicode o Auto completion o Function syntax calltips o Run, run with argument, stop python source o Auto change current path o Python class browser * Code snippets o You can manage your code snippets with categories, and each category can have many items. Every item will represent a code snippet. You can insert an item just by double-clicking on it. It even supports importing and exporting. * Simple project support o Can create a special file _project, so every file and folder under the folder which has the _project can be considered as a whole project. * Extension mechanism o Script -- You can write easy script to manipulate the all resource of NewEdit, just like: text conversion, etc. o Plugin -- Customized function. More complex but more powerful. Can easily merge with NewEdit, and can be managed via menu. o Shell command -- Add often used shell commands, and execute them. * Ftp support o You can edit remote files through ftp. You can add, rename, delete, upload, download file/directory. * Multilanguage support o Currently supports two languages: English and Chinese, which can be auto-detected. * Shipped plugins(must be configed as used them before) o Document links -- Python documentation and wxPython documentation. o Many plugins can be found at NewEdit wiki page. * Shipped scripts o Many scripts can be found at NewEdit wiki page. * Wizard (New) o You can make your own wizard template. The wizard can input user data, combine with template, and output the result. And wizard also support code framework created. This feature will help you improving coding efficiency. * Direcotry Browser(New) o Browse multiple directories, and you can really add, delete, rename directories and files. Double click will open the file in Editor window. * AutoComPlete(acp)(New) o Suport user autocomplete file, it can help to input code very helpful and functional. Just like EditPlus, but may be more powerful. Where to download it? ================ download lastest version 3.1: http://wiki.woodpecker.org.cn/moin/NewEdit?action=AttachFile&do=get&target=… also have windows installer: http://wiki.woodpecker.org.cn/moin/NewEdit?action=AttachFile&do=get&target=… wiki: http://wiki.woodpecker.org.cn/moin/NewEdit svn: http://cvs.woodpecker.org.cn/svn/woodpecker/newedit maillist: http://groups.google.com/group/NewEdit If you have any problem as using NewEdit, welcome to join the NewEdit maillist to discuss. Hope fun! -- I like python! My Blog: http://www.donews.net/limodou NewEdit Maillist: http://groups.google.com/group/NewEdit

1 0

ANN: Karrigell-2.2 final released
by Pierre Quentel Nov. 21, 2005

Nov. 21, 2005

The definitive 2.2 version of Karrigell, a Python web framework, has been released at http://karrigell.sourceforge.net The main changes in this version are the support of Virtual Hosts and the inclusion of the Cheetah templating system This final release fixes 2 bugs, one in the asynchronous HTTP server which would use 100% of the CPU in some cases, and another one in the protected directory management Best regards, Pierre

1 0