Re: [Python-Dev] Python Unit Tests
Wesley Mesquita wrote: > Hi all, > > I starting to explore python 3k core development environment. So, sorry in > advance for any mistakes, but I really don't know what is the best list to > post this, since it not a "use of python" issue, and probably is not a dev > issue, it is more like a "dev env" question. > > I have ran the test suit, and got the messages below. > > ~/python_dev/python$ make testall > > ./python -Wd -E -bb ./Lib/test/regrtest.py -uall -l > == CPython 3.2rc2+ (py3k:88376, Feb 7 2011, 18:31:28) [GCC 4.4.5] > == Linux-2.6.35-24-generic-x86_64-with-debian-squeeze-sid little-endian > == /home/wesley/python_dev/python/build/test_python_3387 > Testing with flags: sys.flags(debug=0, division_warning=0, inspect=0, > interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, > ignore_environment=1, verbose=0, bytes_warning=2, quiet=0) > > [...] > > [198/349] test_ossaudiodev > test_ossaudiodev skipped -- [Errno 2] No such file or directory: '/dev/dsp' > > [...] > > [200/349] test_parser > Expecting 's_push: parser stack overflow' in next line > s_push: parser stack overflow > > [...] > > [321/349] test_urllib2net > /home/wesley/python_dev/python/Lib/socket.py:333: ResourceWarning: unclosed > > self._sock = None > /home/wesley/python_dev/python/Lib/urllib/request.py:2134: ResourceWarning: > unclosed > sys.exc_info()[2]) > /home/wesley/python_dev/python/Lib/urllib/request.py:2134: ResourceWarning: > unclosed > sys.exc_info()[2]) > /home/wesley/python_dev/python/Lib/socket.py:333: ResourceWarning: unclosed > > self._sock = None > /home/wesley/python_dev/python/Lib/socket.py:333: ResourceWarning: unclosed > > self._sock = None > /home/wesley/python_dev/python/Lib/socket.py:333: ResourceWarning: unclosed > > self._sock = None > /home/wesley/python_dev/python/Lib/socket.py:333: ResourceWarning: unclosed > > self._sock = None > [323/349] test_urllibnet > /home/wesley/python_dev/python/Lib/socket.py:333: ResourceWarning: unclosed > > self._sock = None > > > 24 tests skipped: > test_bz2 test_curses test_dbm_gnu test_dbm_ndbm test_gdb > test_kqueue test_ossaudiodev test_readline test_smtpnet > test_socketserver test_sqlite test_ssl test_startfile test_tcl > test_timeout test_tk test_ttk_guionly test_ttk_textonly > test_urllib2net test_urllibnet test_winreg test_winsound > test_xmlrpc_net test_zipfile64 > 9 skips unexpected on linux2: > test_bz2 test_dbm_gnu test_dbm_ndbm test_readline test_ssl > test_tcl test_tk test_ttk_guionly test_ttk_textonly > sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name='/dev/null' > mode='a' encoding='UTF-8'> > > > But running each of them individually: > > :~/python_dev/python$ ./python Lib/test/regrtest.py test_ossaudiodev > [1/1] test_ossaudiodev > test_ossaudiodev skipped -- Use of the `audio' resource not enabled > 1 test skipped: > test_ossaudiodev > Those skips are all expected on linux2. > > ./python Lib/test/regrtest.py test_parser > [1/1] test_parser > Expecting 's_push: parser stack overflow' in next line > s_push: parser stack overflow > 1 test OK. > > ./python Lib/test/regrtest.py test_urllib2net[1/1] test_urllib2net > test_urllib2net skipped -- Use of the `network' resource not enabled > 1 test skipped: > test_urllib2net > Those skips are all expected on linux2. > > Is there any reason for the different results? Yes: you are not using the same options on the stand-alone tests as you are on the suite run. Most importantly, you are not enabling all resources (-uall). -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Feb 08 2011) >>> Python/Zope Consulting and Support ...http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/ ::: Try our new mxODBC.Connect Python Database Interface for free ! eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] devguide: Basic instructions on how to generate a patch with hg for non-committers.
On Sun, 6 Feb 2011 12:13:08 -0800 Brett Cannon wrote: > > > > We could perhaps present SVN-like "work in the working copy" workflow > > (without local commits), and let seasoned hg users choose other > > workflows they like more (they don't need our help anyway). > > I would rather give people some simple workflow that has some benefit > over svn. Basically whatever is the easiest to comprehend and work > with should be what we start people with. Ok, I've updated the devguide to present a simple named branch-based approach. I'm not sure it is our job to *explain* hg features, so I've just given a couple of minimal instructions to get people on track. Regards Antoine. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python Unit Tests
On Tue, Feb 8, 2011 at 11:00 AM, R. David Murray wrote: > There are some ResourceWarnings we haven't cured yet (the ResourceWarning is > a fairly new innovation). I'm not sure why they don't show up when > you run the tests individually. Almost certainly the missing "-uall" meant the relevant tests didn't actually run the second time around. >> 9 skips unexpected on linux2: >> test_bz2 test_dbm_gnu test_dbm_ndbm test_readline test_ssl >> test_tcl test_tk test_ttk_guionly test_ttk_textonly > > These would be because you don't have the correct system/development > libraries installed for bz2, gnudbm, ndbm, readline, openssl, > tcl, and tk when you compiled your Python. So, these skips are > actually expected if you don't have those libraries, but if you want > a complete development/test environment you should install the > necessary packages and recompile. I put together a list a while back of the minimal set of dev packages needed to do a full Python build on Kubuntu: http://www.boredomandlaziness.org/2010/01/kubuntu-dev-packages-to-build-python.html The apt-get build dependencies command added as a comment to that post should work on any apt-based Linux variant (although, at least on Kubuntu, it brings down quite a lot of stuff you don't actually need in order to build Python). Presumably there's something similar available for other packaging systems (if not, the minimal package list may still provide a useful starting point) I don't believe anything that platform specific is in the dev guide, though (it wasn't in the old README files, that's why I made my own list for later reference). Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] http://www.pythonlabs.com/logos.html is gone
As a late follow-up to this thread, I still get a bunch of hits a day on this URL (and also on www.pythonlabs.com/talks.html -- I have no idea what popular page *that* is still linked from). I don't suppose we can *ever* delete that link from the LICENSE file? On Sun, Oct 11, 2009 at 1:46 PM, Georg Brandl wrote: > Guido van Rossum schrieb: >> On Sun, Oct 11, 2009 at 12:55 PM, Georg Brandl wrote: >>> Which I noticed since it's cited in the BeOpen license we still refer >>> to in LICENSE. Since pythonlabs.com itself is still up, it probably >>> isn't much work to make the logos.html URI work again, but I don't know >>> who maintains that page. >> >> I own the domain. I don't know what was on logos.html and >> http://web.archive.org won't show it to me because of a robots.txt >> file. I think it's fine to let it be a 404. > > Okay. Though I am fairly sure that Tim *would* remember ;) > > Georg > > -- > Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. > Four shall be the number of spaces thou shalt indent, and the number of thy > indenting shall be four. Eight shalt thou not indent, nor either indent thou > two, excepting that thou then proceed to four. Tabs are right out. > > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] devguide: Basic instructions on how to generate a patch with hg for non-committers.
On Tue, Feb 8, 2011 at 05:26, Antoine Pitrou wrote: > On Sun, 6 Feb 2011 12:13:08 -0800 > Brett Cannon wrote: >> > >> > We could perhaps present SVN-like "work in the working copy" workflow >> > (without local commits), and let seasoned hg users choose other >> > workflows they like more (they don't need our help anyway). >> >> I would rather give people some simple workflow that has some benefit >> over svn. Basically whatever is the easiest to comprehend and work >> with should be what we start people with. > > Ok, I've updated the devguide to present a simple named branch-based > approach. I'm not sure it is our job to *explain* hg features, so I've > just given a couple of minimal instructions to get people on track. Yep, what you wrote is what I was thinking. Enough so people can get up and going and at least a taste of what hg can do for them w/o devolving into an hg tutorial. -Brett > > Regards > > Antoine. > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/brett%40python.org > ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] devguide: Try to explain the two most common approaches to hg workflow: feature
fixed On Tue, Feb 8, 2011 at 14:27, Terry Reedy wrote: > >> +While non-committers can use named branches without issue, as a core >> developer >> +you should limit their use to only those branches to be used to >> collaborate > > either /their/your/ > or /as a core developer you/core developers/ > I prefer latter as parallel to 'non-committers'. > ___ > Python-checkins mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-checkins > ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
