🌐 Mailman 3 January 2004 - Python-list - python.org

Re: Tcp/ip programs in python
by Josiah Carlson Jan. 31, 2004

Jan. 31, 2004

Jp Calderone wrote: > On Fri, Jan 30, 2004 at 06:27:45PM -0000, M.Dikmen wrote: > >>Do you now a source about socket programming in python? or some source >>codes, demo programs? i really need them >> > > > In order of increasing relevance: > > http://www.google.com/ > > http://www.vex.net/parnassus/ > > http://www.twistedmatrix.com/ I always found http://www.python.org/doc/current/lib/module-socket.html to be quite useful for the background and http://www.python.org/doc/current/lib/module-asyncore.html for the actual implementation. - Josiah

2 1

Chart drawing library for Python
by llothar＠web.de Jan. 31, 2004

Jan. 31, 2004

Hello, is there something like "JpGraph" for python ? For those who don't know this PHP library: It is a high level drawing library that generates gif files with all kind of charts. Or (maybe better) is there a C library doing this. I think i read about something like this a while ago.

5 6

Our Anti-Vrus system found VIRUS= MyDoom.A@m (Norman, CA(Vet), Kaspersky) worm
by Antigen_EXCHANGE_MTL＠smtp.cidc.net Jan. 31, 2004

Jan. 31, 2004

Our Anti-Vrus system found doc.zip->doc.exe infected with VIRUS= MyDoom.A@m (Norman,CA(Vet),Kaspersky) worm. The message is currently Purged. The message, "Test", was sent from python-list(a)python.org

1 0

Re: RESTful Python
by A.M. Kuchling Jan. 31, 2004

Jan. 31, 2004

On Fri, 30 Jan 2004 13:39:02 +0800, SimonW <drconrad(a)metaplay.com.au> wrote: > I want to be able to address sections of an XML document using an URI, > but I am not sure how to implement this. I've seen this done in Python > before, however I cannot find the site again, and cannot recall the > correct google incantations to re-discover it. The usual way would be to use a fragment identifier, so that the client can find the right element, e.g. http://example.com/foo.xml#id45 means downloading foo.xml and looking for the element with an id="id45" attribute. But the fragment identifier isn't sent to the HTTP server, so you couldn't do a DEL or PUT to replace just that fragment; I don't know if that's what you want. > Can anyone point me to some REST style implementations in Python? Someone's already pointed you to Dave Kuhlman's article on REST and Quixote, which is a good start. --amk

1 0

Get error "ImportError: No module named _tkinter"
by Sebastian Stelzer Jan. 31, 2004

Jan. 31, 2004

Hi, I'am a beginner in Python and I have got a problem with the TKInter module. When I want to start e.g. pysol, I get following output: [output] Traceback (most recent call last): File "/usr/share/games/pysol/src/pysol.py", line 47, in ? from main import main File "/usr/share/games/pysol/src/main.py", line 48, in ? from app import Application File "/usr/share/games/pysol/src/app.py", line 54, in ? from images import Images, SubsampledImages File "/usr/share/games/pysol/src/images.py", line 47, in ? from pysoltk import tkversion, loadImage, copyImage, createImage File "/usr/share/games/pysol/src/pysoltk.py", line 81, in ? exec "from " + m + " import *" File "<string>", line 1, in ? File "/usr/share/games/pysol/src/tk/tkconst.py", line 39, in ? import Tkinter File "/usr/local/lib/python2.3/lib-tk/Tkinter.py", line 38, in ? import _tkinter # If this fails your Python may not be configured for Tk ImportError: No module named _tkinter [/output] I'am using Suse Linux 9.0 with Python 2.3.3. Can anybody help me? cu

2 3

Re: Suggested generator to add to threading module.
by Alan Kennedy Jan. 31, 2004

Jan. 31, 2004

[Andrae Muys] >>> Found myself needing serialised access to a shared generator from >>> multiple threads. Came up with the following >>> >>> def serialise(gen): >>> lock = threading.Lock() >>> while 1: >>> lock.acquire() >>> try: >>> next = gen.next() >>> finally: >>> lock.release() >>> yield next [Ype Kingma] >> Is there any reason why the lock is not shared among threads? >> From the looks of this, it doesn't synchronize anything >> between different threads. Am I missing something? [Jeff Epler] > Yes, I think so. You'd use the same "serialise" generator object in > multiple threads, like this: > > p = seralise(producer_generator()) > threads = [thread.start_new(worker_thread, (p,)) > for t in range(num_workers)] Hmm. I think Ype is right: the above code does not correctly serialise access to a generator. The above serialise function is a generator which wraps a generator. This presumably is in order to prevent the wrapped generators .next() method being called simultaneously from multiple threads (which is barred: PEP 255: "Restriction: A generator cannot be resumed while it is actively running") http://www.python.org/peps/pep-0255.html However, the above implementation re-creates the problem by using an outer generator to wrap the inner one. The outer's .next() method will then potentially be called simultaneously by multiple threads. The following code illustrates the problem #-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= import time import thread import threading def serialise(gen): lock = threading.Lock() while 1: lock.acquire() try: next = gen.next() finally: lock.release() yield next def squares(n): i = 1 while i < n: yield i*i i = i+1 def worker_thread(iter, markers): markers[thread.get_ident()] = 1 results = [] ; clashes = 0 while 1: try: results.append(iter.next()) except StopIteration: break except ValueError, ve: if str(ve) == "generator already executing": clashes = clashes + 1 del markers[thread.get_ident()] print "Thread %5s: %d results: %d clashes." % (thread.get_ident(),\ len(results), clashes) numthreads = 10 ; threadmarkers = {} serp = serialise(squares(100)) threads = [thread.start_new_thread(worker_thread,\ (serp, threadmarkers)) for t in xrange(numthreads)] while len(threadmarkers.keys()) > 0: time.sleep(0.1) #-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I believe that the following definition of serialise will correct the problem (IFF I've understood the problem correctly :-) #-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= import time import thread import threading class serialise: "Wrap a generator in an iterator for thread-safe access" def __init__(self, gen): self.lock = threading.Lock() self.gen = gen def __iter__(self): return self def next(self): self.lock.acquire() try: return self.gen.next() finally: self.lock.release() def squares(n): i = 1 while i < n: yield i*i i = i+1 def worker_thread(iter, markers): markers[thread.get_ident()] = 1 results = [] ; clashes = 0 while 1: try: results.append(iter.next()) except StopIteration: break except ValueError, ve: if str(ve) == "generator already executing": clashes = clashes + 1 del markers[thread.get_ident()] print "Thread %5s: %d results: %d clashes." % (thread.get_ident(),\ len(results), clashes) numthreads = 10 ; threadmarkers = {} serp = serialise(squares(100)) threads = [thread.start_new_thread(worker_thread,\ (serp, threadmarkers)) for t in xrange(numthreads)] while len(threadmarkers.keys()) > 0: time.sleep(0.1) #-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Also, I don't know if I'm happy with relying on the fact that the generator raises StopIteration for *every* .next() call after the actual generated sequence has ended. The above code depends on the exhausted generator raising StopIteration in every thread. This seems to me the kind of thing that might be python-implementation specific. For example, the original "Simple Generators" specification, PEP 255, makes no mention of expected behaviour of generators when multiple calls are made to the its .next() method after the iteration is exhausted. That I can see anyway? Am I wrong? http://www.python.org/peps/pep-0255.html regards, -- alan kennedy ------------------------------------------------------ check http headers here: http://xhaus.com/headers email alan: http://xhaus.com/contact/alan

6 9

ALCATEL POLICY : your message has been refused
by support＠alcanet.com.au Jan. 31, 2004

Jan. 31, 2004

******************** e-mail Manager Notification ********************** As a security precaution this mail was blocked and discarded since it contains attachments with file extensions not allowed by our email policy (.exe, .vbs etc ...) Source mailbox : <python-list(a)python.org> Destination mailbox : <james(a)alcatel.com.au> Message Subject : Hello Attachment: application/octet-stream; name="eekdco.pif" Our mail system policy does not accept certain attachment types. See http://www.alcatel.com/mail_policy/email_attachments.htm for additional details. Please zip up the file and send again or use an alternate method to send the file. If you have questions, contact your local email support representative. ********************** End of message ***************************

1 0

Re: win32com - .ocx won't Dispatch...
by Mark Hammond Jan. 31, 2004

Jan. 31, 2004

Ray Schumacher wrote: > So, the util class Dispatches, but all calls (properties and functions) give 'Catastrophic failure' > Is this really some sort of types problem with this OCX? > "pywintypes.com_error: (-2147418113, 'Catastrophic failure', None, None)" My guess is that your OCX is a true OCX, and therefore needs a full GUI environment. Pythonwin can host these - see the pythonwin\pywin\demos\ocx directory, and modify one of these to suit. wxPython can also apparently host OCX controls in a similar way, but I have no details. Mark.

2 1

Re: mod_speling for python
by Josiah Carlson Jan. 30, 2004

Jan. 30, 2004

Skip Montanaro wrote: > >> I know there are drawbacks, disadvantages, this is "evil", etc. I > >> only wanted to know what ways there are to add such a hook if it is > >> possible without altering the C source for python itself. > > Josiah> Ambiguities during execution are bad. I've got two functions > Josiah> Foo and foO, if I type in foo, what did I mean? > > I didn't interpret the OP's question as wanting to automatically map Foo to > foO, but to give the user a more helpful error message, suggesting other > candidate names which he might have mistyped. That could be useful, if what you say is actually what he meant. - Josiah

2 1

Re: Problems with python23_d.lib built with Visual Studio 7.1
by Mark Hammond Jan. 30, 2004

Jan. 30, 2004

Paton J. Lewis wrote: > I built the Python 2.3.3 sources with Visual Studio 7.1 (the > conversion of the Visual C++ 6 project files appeared to work > without a hitch). Everything seems fine except when I try to link my > project with the debug Python library, in which case I get > unresolved symbols apparently because the Python debug library > symbol names have been modified in an unexpected fashion. For > example, the calling code asks for symbol __imp__Py_InitModule4 > (which exists in python23.lib) but python23_d.lib contains > __imp__Py_InitModule4TraceRefs. Has anyone run into this problem > before? It sounds to me like you are trying to link your non-debug built extension module with a debug built Python. A debug built extension module will not have a reference to __imp__Py_InitModule4. Make sure the code you are trying to link against Python23_d.dll is compiled with /DDEBUG /D_DEBUG and /MDd. Mark.

1 0