🌐 Mailman 3 September 2001 - Python-list - python.org

Re: Threads in Solaris?
by Georg Lohrer Sept. 29, 2001

Sept. 29, 2001

On Fri, 28 Sep 2001 22:01:42 -0000, jwray(a)mifund.com wrote: >I wrote a threaded app on my win2k box, not realizing that threads >weren't part of the standard python install. Now that i want to >install my code on a solaris box it complains that it doesn't have >thread.py. I would copy the one from my win2k box, but it imports >win32, which I'm sure wouldn't work out. > >So my question is, where can I get a threading module for solaris? >I've read off verious sites that one exists, but I haven't been able >to find it for download. First of all, I've made the Solaris-stuff from scratch out of the tar.gz-source-archive file (Python-2.1.tgz) and threading is running very well. Compiling was not as easy as within Linux, but that's caused by our equipment. I don't know whether it might be possible or even senseful only copying threading.py to another system, because most of these moduls rely on underlying C-modules. And even if you copy these modules, too, they won't run under Solaris, do they. Ciao, Georg

1 0

A neat text link exchang website
by link99 Sept. 29, 2001

Sept. 29, 2001

http://go.to/link99 It's Coool! You'll get a neat exchanging link, and never get messy!

1 0

Re: doctest suggestion
by Tim Hochberg Sept. 29, 2001

Sept. 29, 2001

Right behind avoiding land wars in Asia is some advice about not arguing with Tim Peters, but why be prudent. > > However, I frequently run into problems when I import a class or > > function from a module using "from X import Y". > > So don't do that. I don't. Because the import of a name also implicitly > *exports* the name to users of "import *", that's sloppy practice and > doctest deliberately didn't cater to it (read the doctest docs: they're > quite explicit about this). Yes, but sometimes one deliberately exposes imported names, and then things break even thouigh one's not being sloppy. Back when I was using "import Y as _Y" I had particular problems with "__init__.py" files where I sometimes pulled in several functions or classes from different modules. > In recent Pythons "from X import Y as _Y" is a > one-liner way to rename Y to use a private name, and then doctest ignores > it, and you also don't screw import-* users. I've decided not to cater to import * users. I've banned import-* from code and what made it painless enough for me do was "import Numeric as np". My advice to users of "from X import *" is generally "So don't do that." Hmmm. Sounds familiar somehow. > Other possibilities include > passing your own isprivate function to doctest, or passing a module dict > pruned of names you don't want to see tested. I automate running doctest by walking all the packages and running doctest everywhere. isprivate isn't powerful enough to help me here since it only works on names. The second solution sounds like it might work -- I'll look into it. [Snip] > Right; and the doctest docs point this out. Yeah, I knew that... [Snap] > However, I'd accept a SourceForge patch > *provided that* it also leaves doctest working correctly under Jython. > doctest plays very mild introspection games, because Jython doesn't support > the same set of internal __xxx__ magic attributes CPython supports. I don't > know whether your use of __xxx__ tricks works under Jython too; if it does, > cool, else it's a show-stopper. I don't have the motivation (since I don't > do what you're doing) to dig into this myself. But if someone else does, > incl. enough motivation to verify Jython behavior, and to change the docs > and the doctest tests, happy to play along. The last person who tried to > address this, about two years ago, didn't find a way that also worked under > Jython. Fair enough. I'll either look into the Jython side, or put together a solution based on pruning the dictionary -- either way you won't have to listen to me whining again for a while.... -tim

1 0

test
by link99 Sept. 29, 2001

Sept. 29, 2001

test

1 0

Python an WindowsCE on x86
by dag4004 Sept. 29, 2001

Sept. 29, 2001

Hello, Is it possible to use Python on a WindowsCE (x86) platform ? Where could i find it ? Thanks

2 1

Re: Importing MySQLdb/Changing Paths at run-time
by mund33p＠yahoo.com.au Sept. 29, 2001

Sept. 29, 2001

Sam Penrose <sam(a)ddmweb.com> wrote in message news:<mailman.1001711011.32097.python-list(a)python.org>... > import sys > sys.path.append('whatever') > that doesnt't seem to work either. I tried instead moving the MySQLdb module to the cgi-bin directory and it now seems to find it but gives me the following error: Import error ld.so.1: /usr/local/bin/python: fatal: libz.so.1: open failed: No such file or directory Anyone know what this means? > always works for me. I'm not sure why the near-equivalent isn't working > for you. > > You can also set the PYTHONPATH environment variable for the cgi user > though it sounds like this may be unworkable in your situtation. Our > httpd.conf files have a line that reads: > > SetEnv PYTHONPATH /home/httpd/shared/cgi-bin Unfortunately dont have access to modify any webserver settings. Cheers, Mundeep

1 0

Problem with os.system()
by Janos Blazi Sept. 29, 2001

Sept. 29, 2001

I have the following code: -----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- http://www.newsfeeds.com - The #1 Newsgroup Service in the World! Check out our new Unlimited Server. No Download or Time Limits! -----== Over 80,000 Newsgroups - 19 Different Servers! ==-----

3 2

Best way to learn Python?
by Sam Scholey Sept. 29, 2001

Sept. 29, 2001

Hi Again, I have read material online from many excellent linux hackers that the best way to learn code is first to read code then write code, and not books. Is this true? Are any of you completely self-taught and fluent in Python? Thanks

8 9

Re: file find module
by Peter Hansen Sept. 29, 2001

Sept. 29, 2001

Chris Gonnerman wrote: > Peter Hansen wrote: > > Just be careful because glob.glob('*') will not return filenames > > that start with a period, while glob.glob('.*') will return only > > such filenames. You need both if you want all files. > > Use os.listdir() and write your own matching function if the dotfiles > become a problem. ... and write code to prepend the full path to the matched files ... and recurse to support multi-segment matching: glob.glob('*/*/*.c') ... and ? probably some other things that aren't immediately apparent (It's likely easier to use glob in many cases, which is why I think it's still a nice option, just one which ought to have improved documentation for non-Unix heads...) -- ---------------------- Peter Hansen, P.Eng. peter(a)engcorp.com

1 0

Re: doctest suggestion
by Tim Hochberg Sept. 29, 2001

Sept. 29, 2001

[Sorry, my stupid mailer sent this before I was ready.] Hi all and particularly Tim Peters if your listening, I like doctest a lot and use it for all of my unit testing. However, I frequently run into problems when I import a class or function from a module using "from X import Y". Y's docstring gets run in the current environment and frequently the doctests fail because they rely on some aspects of Xs environment. It seemed like it would be useful to skip tests in docstrings on objects imported from another module. I threw together a proof of concept of this which is attached below; this version ignores the docstrings on imported functions and classes. So here's the suggestion: I would really like to see this functionality included in doctest in some way. I'm willing to clean up the changes to my code and submit a patch if that's appropriate. However, first I wanted solicit opinions as to whether this approach is a good one or if there's a more elegant way to go about it: -tim Here are the two changed parts, the method rundict from Tester and the function testmod: def rundict(self, d, name, module=None): # Docstring elided if not hasattr(d, "items"): raise TypeError("Tester.rundict: d must support .items(); " + `d`) f = t = 0 # Run the tests by alpha order of names, for consistency in # verbose-mode output. names = d.keys() names.sort() for thisname in names: value = d[thisname] # Stuff in this if statement is new.... if type(value) in (_FunctionType, _ClassType): if module is not None: if (type(value) == _FunctionType) and (value.func_globals != module.__dict__): continue if (type(value) == _ClassType) and (value.__module__ != module): continue f2, t2 = self.__runone(value, name + "." + thisname) f = f + f2 t = t + t2 return f, t def testmod(m, name=None, globs=None, verbose=None, isprivate=None, report=1): # docstring elided... global master if type(m) is not _ModuleType: raise TypeError("testmod: module required; " + `m`) if name is None: name = m.__name__ tester = Tester(m, globs=globs, verbose=verbose, isprivate=isprivate) failures, tries = tester.rundoc(m, name) f, t = tester.rundict(m.__dict__, name, m) # we now pass m in... failures = failures + f tries = tries + t if hasattr(m, "__test__"): testdict = m.__test__ if testdict: if not hasattr(testdict, "items"): raise TypeError("testmod: module.__test__ must support " ".items(); " + `testdict`) f, t = tester.run__test__(testdict, name + ".__test__") failures = failures + f tries = tries + t if report: tester.summarize() if master is None: master = tester else: master.merge(tester) return failures, tries

2 1