🌐 Mailman 3 March 2005 - Python-list - python.org

Met Problem with Distutils
by steven＠lczmsoft.com March 1, 2005

March 1, 2005

if i want a main executable py script installed on the /usr/local/bin, what do i do? i tried the data_files options in the setup.py, but nothing happened, no the expected file appeared in the resulted tarbar. below is the setup.py: setup(name='foopkg', version='1.0', author="Steven Woody", author_email="steven(a)lczmsoft.com", url="http://a.b.c", packages=['foopkg'], scripts=['scripts/*.py'], data_files=[('/usr/local/bin', ['scripts/myprj.py'])] ) can anyone tell me what is wrong? thanks in advance! - narke

2 1

Re: String Replace Problem...
by sean_mcilroy＠yahoo.com March 1, 2005

March 1, 2005

I can't claim to have studied your problem in detail, but I get reasonable results from the following: filename = 'Errors.txt' S = open(filename,'r').read().split() f = lambda x: (x[0]=='@' and x[6:] + '.0') or (x=='/' and x + '\n') or x open(filename,'w').write(' '.join(map(f,S))) HTH ------------------------------------------------------------------------- andrea.gavana(a)agip.it wrote in message news:<mailman.3138.1109605552.22381.python-list(a)python.org>... > Hello NG, > > probably this is a basic question, but I'm going crazy... I am unable > to find an answer. Suppose that I have a file (that I called "Errors.txt") > which contains these lines: > > MULTIPLY > 'PERMX' @PERMX1 1 34 1 20 1 6 / > 'PERMX' @PERMX2 1 34 21 41 1 6 / > 'PERMX' @PERMX3 1 34 1 20 7 14 / > 'PERMX' @PERMX4 1 34 21 41 7 14 / > 'PERMX' @PERMX5 1 34 1 20 15 26 / > 'PERMX' @PERMX6 1 34 21 41 15 26 / > 'PERMX' @PERMX7 1 34 1 20 27 28 / > 'PERMX' @PERMX8 1 34 21 41 27 28 / > 'PERMX' @PERMX9 1 34 1 20 29 34 / > 'PERMX' @PERMX10 1 34 21 41 29 34 / > 'PERMX' @PERMX11 1 34 1 20 35 42 / > 'PERMX' @PERMX12 1 34 21 41 35 42 / > 'PERMX' @PERMX13 1 34 1 20 43 53 / > 'PERMX' @PERMX14 1 34 21 41 43 53 / > 'PERMX' @PERMX15 1 34 1 20 54 61 / > 'PERMX' @PERMX16 1 34 21 41 54 61 / > / > > I would like to replace all the occurrencies of the "keywords" (beginning > with the @ (AT) symbol) with some floating point value. As an example, this > is what I do: > > # --- CODE BEGIN > > import re > import string > > # Set Some Dummy Parameter Values > parametervalues = range(1, 17) > > # Open And Read The File With Keywords > fid = open("Errors.txt","rt") > onread = fid.read() > fid.close() > > # Find All Keywords Starting with @ (AT) > regex = re.compile("[\@]\w+", re.IGNORECASE) > keywords = regex.findall(onread) > > counter = 0 > > # Try To Replace The With Floats > for keys in keywords: > pars = parametervalues[counter] > onread = string.replace(onread, keys, str(float(pars))) > counter = counter + 1 > > # Write A New File With Replaced Values > fid = open("Errors_2.txt","wt") > fid.write(onread) > fid.close() > > # --- CODE END > > > Now, I you try to run this little script, you will see that for keywords > starting from "@PERMX10", the replaced values are WRONG. I don't know why, > Python replace only the "@PERMX1" leaving out the last char of the keyword > (that are 0, 1, 2, 3, 4, 5, 6 ). These values are left in the file and I > don't get the expected result. > > Does anyone have an explanation? What am I doing wrong? > > Thanks to you all for your help. > > Andrea. > > ------------------------------------------------------------------------------------------------------------------------------------------ > Message for the recipient only, if received in error, please notify the > sender and read http://www.eni.it/disclaimer/

2 3

Weekly Python Patch/Bug Summary
by Kurt B. Kaiser March 1, 2005

March 1, 2005

Patch / Bug Summary ___________________ Patches : 303 open ( -5) / 2764 closed ( +9) / 3067 total ( +4) Bugs : 849 open (+11) / 4837 closed ( +3) / 5686 total (+14) RFE : 169 open ( +1) / 148 closed ( +0) / 317 total ( +1) New / Reopened Patches ______________________ New fpconst module (2005-02-24) http://python.org/sf/1151323 opened by Gregory Warnes PyXxx_Check() speed-up (2005-02-27) http://python.org/sf/1153056 opened by Armin Rigo os.remove error on Solaris (2005-02-28) http://python.org/sf/1153417 opened by Richard Philips Patches Closed ______________ rlcompleter does not expand on [ ] (2002-04-22) http://python.org/sf/547176 closed by mwh Non-blocking Socket Server (2004-05-02) http://python.org/sf/946207 closed by loewis add urldecode() method to urllib (2003-05-21) http://python.org/sf/740827 closed by loewis adding bool support to xdrlib.py (2004-10-18) http://python.org/sf/1049151 closed by loewis PEP309 Partial implementation (2004-04-25) http://python.org/sf/941881 closed by rhettinger sanity check for readline remove/replace (2004-12-31) http://python.org/sf/1093585 closed by loewis PEP 309 LaTeX documentation (2004-04-07) http://python.org/sf/931007 closed by rhettinger Build Patch #941881 (PEP 309 in C) on windows (2004-08-10) http://python.org/sf/1006948 closed by rhettinger PEP 309 unit tests (2004-04-07) http://python.org/sf/931010 closed by rhettinger New / Reopened Bugs ___________________ hotshot.runctx: builtins missing (2005-02-23) http://python.org/sf/1149798 opened by Jurjen N.E. Bos macostools.mkdirs: not thread-safe (2005-02-23) http://python.org/sf/1149804 opened by Jurjen N.E. Bos (XMLRPC) multitude of sockets ending up in TIME_WAIT (2005-02-25) http://python.org/sf/1151968 opened by Jonas Widén Dict docstring error Python-2.3.5 (2005-02-26) http://python.org/sf/1152424 opened by Colin J. Williams urllib2 dont respect debuglevel in httplib (2005-02-27) http://python.org/sf/1152723 opened by abbatini Default class args get clobbered by prior instances. (2005-02-26) CLOSED http://python.org/sf/1152726 opened by Simon Drabble curses.textpad raises error (2005-02-27) http://python.org/sf/1152762 opened by John McPherson Setting socket timeout crashes SSL (2005-02-27) http://python.org/sf/1153016 opened by pristine777 http_error_302() crashes with 'HTTP/1.1 400 Bad Request (2005-02-27) http://python.org/sf/1153027 opened by pristine777 PyXxx_Check(x) trusts x->ob_type->tp_mro (2005-02-27) http://python.org/sf/1153075 opened by Armin Rigo reflected operator not used when operands have the same type (2005-02-27) http://python.org/sf/1153163 opened by HughSW reflected operator not used when operands have the same type (2005-02-27) CLOSED http://python.org/sf/1153171 opened by HughSW string interpolation breaks with %d and large float (2005-02-28) http://python.org/sf/1153226 opened by Stephen Thorne eval does not bind variables in lambda bodies correctly (2005-02-28) http://python.org/sf/1153622 opened by Mattias Engdegård String interpolation needs PEP 237 update (2005-02-28) http://python.org/sf/1153769 opened by Richard Brodie Bugs Closed ___________ Python24.dll crashes, EXAMPLE ATTACHED (2005-02-12) http://python.org/sf/1121201 closed by complex Default class args get clobbered by prior instances. (2005-02-26) http://python.org/sf/1152726 closed by rhettinger reflected operator not used when operands have the same type (2005-02-27) http://python.org/sf/1153171 closed by rhettinger New / Reopened RFE __________________ Enhance file.readlines by making line separator selectable (2005-02-26) http://python.org/sf/1152248 opened by Nick Coghlan

1 0

Re: best XSLT processor?
by uche.ogbuji＠gmail.com March 1, 2005

March 1, 2005

Xalan is certainly faster, but it is almost certainly not more compliant than 4Suite. Xalan actually has a bit of a reputation among XSLT processors in its carelessness with compliance. But I suppoose in order to settle these counter-claims, one of us will have to come up with specific compliance examples. You fired the first shot. Can you back it up? --Uche

1 1

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

Share your SciTEGlobal.properties pls~~~~
by DENG March 1, 2005

March 1, 2005

hi, im new to Python, i chose SciTE as my Python editor. but the problem is SciTE needs to be config carefully, are there anyone use SciTE too? can you share your SciTEGlobal.properties file? black background solution is prefered:) thanks in advance best regards

2 1

Pythonwin: Red squiggley underline and syntax error
by Brent W. Hughes March 1, 2005

March 1, 2005

I copied and pasted some text into my Python code and then Pythowin put a red squiggley underline under the two tabs at the beginning of the line. What does that mean? I've tried various things including deleting the white space in front of the line and reinserting the tabs. I've also tried retyping the entire line. Sometimes, I can get the red line to go away but when I try to run the program, it gives me a syntax error on the line that had the red underline. Help! Brent

4 3

Hey, How Do I Distribute my New Completed Python Project?
by steven＠lczmsoft.com March 1, 2005

March 1, 2005

I'v just completed a small python project, which includes a main py file and a couple of classes in seperated py files. I can run it under the development directory, but how to distribute them? Is there any good practice here? Thanks in advance. - narke

3 3

Re: Problem When Unit Testing with PMock
by steven＠lczmsoft.com March 1, 2005

March 1, 2005

Peter, for a object foo who need a iterator to do a job, i write test to make sure the foo correctlly used the iterator, so a simple empty iterator is not enough. because in the case, i need to see if or not the foo called the iterator to get the proper data from it and do the proper translating on them. so, the mock iterator i need should be such an iterator which can returns be iterated out a lot of test data as i willed. i guess you are not familar with unit testing. we need mock objects not because they are hard to implemented, we need them to make the tests easy and fine. - narke

2 2