[Python-Dev] light-weight testing
Steven D'Aprano pearwood.info> writes: > > I am interested in this suggestion. I didn't know about py.test. > > I admit to dissatisfaction with unittest (too Java-ish and heavyweight > for my tastes). I would love a test suite midway in weight between > doctests and unittest, so I will check it out. > For what it's worth, I've been using nose for quite a long time and the first reason I did so is, like you, because I wanted to write tests in a light way (without having to declare classes). Then after writing some dozens of tests I switched back to wrapping tests in classes, just because it makes tests more readable and better organized (especially when you come to have setup/teardown functions shared by several tests). (but nose is still very nice) ___ 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
[Python-Dev] assertRaises
Fred Drake acm.org> writes: > > Sounds like adding a new method, catchException(...), that returns the > exception it catches, would be a reasonable compromise. I can't think > of any reason that the method that catches-and-returns needs to be the > existing API, which does something different. So you'd have a method that just catches (assertRaises), and another one that catches-and-returns (catchException)? It doesn't seem very practical to have two different methods based on such a small and trivial difference. Let's just make assertRaises return the exception instance, it seems like it feels the need correctly. ___ 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] assertRaises
I said: > Let's just make assertRaises return the exception instance, it seems like it > feels the need correctly. and I meant "fills", not "feels", obviously... ___ 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] Unittest PEP do's and don'ts (BDFL pronouncement)
Ben Finney wrote: The function name should say *all* that the function does, from the perspective of the caller. I have to disagree with that (and I think you'll find plenty of other folks here will disagree as well). A good function names needs to have a few characters: - serve as a mnemonic reminder as to what the function does for a programmer already familiar with the API - allow a less familiar user to easily look it up in the API documentation - be easy to remember to make the transition to familiarity with the API as rapid as possible Wanting to say *everything* a function does in its name is an utterly unreasonable goal that leads to ridiculously long function names that nobody can remember. Taking an existing function such as assertRaises and going "hey, we aren't using the return value from this, wouldn't it be really convenient if it told us the exact exception it actually caught?" doesn't cause any problems for existing code, and makes it much easier to write tests that need to check additional details about the exception that is raised (e.g. to check that the correct error code is captured and reported for things like OSError). The essence of the function remains unchanged - you're still asserting that a particular exception is raised. Returning the actual exception object that was caught is merely a convenience that makes a lot of sense. Try to think of it as being like adding a new optional argument to a function - just because the function now provides more flexibility is no reason to change it's name (e.g. when the key and reversed parameters were added to list.sort, the method name stayed the same). Taking an unused return value and making it meaningful is a similar kind of change. Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.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] light-weight testing
Antoine Pitrou wrote: (especially when you come to have setup/teardown functions shared by several tests). These days, I tend to just write a context manager for common setup/teardown code rather than using the setUp/tearDown hooks (at least for Python's own test suite, where I have the luxury of assuming 2.5+ as the Python version). Where I find unittest.TestCase quite convenient is when I want to run the same set of tests with a few different settings - for those, putting the settings into class attributes and then inheriting from the basic test case and using different values is very convenient. This trick is particularly useful for testing that a class supports inheritance properly. Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.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] light-weight testing
Antoine Pitrou <[EMAIL PROTECTED]> writes: > For what it's worth, I've been using nose for quite a long time and > the first reason I did so is, like you, because I wanted to write > tests in a light way (without having to declare classes). > > Then after writing some dozens of tests I switched back to wrapping > tests in classes, just because it makes tests more readable and > better organized (especially when you come to have setup/teardown > functions shared by several tests). > > (but nose is still very nice) It's also entirely compatible with wrapping one's tests in classes. The test discovery and collection in 'nose' is one of the attractions: it discovers them at package, module, class, and plain-function level, whether doctest or not, whether unittest or not, and collects them all to run. -- \ “Well, my brother says Hello. So, hooray for speech therapy.” | `\ —Emo Philips | _o__) | Ben Finney ___ 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] No beta2 tonight
On Thu, Jul 17, 2008 at 12:30 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We have green buildbots, yay! Thanks everyone for that. > > However, we still have three release blocker issues that I am not > comfortable deferring. > > 3088 test_multiprocessing hangs intermittently on POSIX platforms > 3375 _multiprocessing.so build problems > 874900 threading module can deadlock after fork > > My biggest concern is 3375 and 3088, the latter has a dependency on 874900. > > 3375 is very strange since a subsequent 'make' completes just fine. This > issue happens for me on both OS X 10.5 and Ubuntu 8.04 for py3k. > > 3088 does not appear to be happening now on OS X or Ubuntu, but the issue > (and its dependent issue) are not closed, so I'm not sure exactly what's > going on here. > > So we'll give these releases another 24 hours. Please, if you have time see > what you can do about resolving these three blockers. Chat with me on > #python-dev if you think we should release anyway. I will try to look into > 3375, but I'd like to know if anybody else is seeing these build failures. > > I'll note that I plan to hold the beta3 releases until all release blocker > and deferred blockers are resolved. > > - -Barry > Quick status update, since I'm the gating factor. 3088: I didn't want to close this until 874900's patch was submitted, ported to py3k and I saw green build bots. By the time I went to sleep last night, we were still seeing 2to3 test timeouts on the build bots. I will port the patch to 3k today and lower the priority of 874900 and close 3088 shortly. 3375: Guido (thanks guido) looked into this, and while I banged my head on it a lot yesterday - guido's identified the issue, and now I need to figure out a fix - help is welcome on this one. I apologize for not getting these resolved last night -jesse ___ 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] No beta2 tonight
Barry Warsaw wrote: [...] I'll note that I plan to hold the beta3 releases until all release blocker and deferred blockers are resolved. Ian Ozsvald of ShowMeDo.com noticed a blog post of mine about this beta, and responded as follows: Re. http://holdenweb.blogspot.com/2008/07/cpython-getting-serious-about-quality.html If someone on the dev side wanted to make a 5-10 minute 'cast on how to check out the python base, build it, test it, check stuff back in, we'd be honoured to host it. Obviously the entire process deserves more attention but a short overview pointing out the key steps would be: 1) simple for the author to create 2) easy for possible contributors to watch and receive inspiration 3) powerful enough to attract another set of developers into the fold so that might be a useful, low-cost, quick win to help with the current effort? I'd do this myself but a) I'm not the obvious candidate and b) I'm too busy to give it my attention now. If someone wanted to tackle this, it might help getting people testing for the next beta, and also to recruit more testers in the long-term. regards Steve -- Steve Holden+1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ ___ 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-3000] No beta2 tonight
On Thu, Jul 17, 2008 at 6:16 AM, Jesse Noller <[EMAIL PROTECTED]> wrote: > 3375: Guido (thanks guido) looked into this, and while I banged my > head on it a lot yesterday - guido's identified the issue, and now I > need to figure out a fix - help is welcome on this one. You're welcome. I would have never found this if I hadn't had a heightened awareness of the sys.path_importer_cache variable recently, due to implementing a zipimport.py for Google App Engine. :-) I can try looking for a fix later today (in a few hours). A very crude fix would be to just remove all keys that have NullImporter values from that variable just before attempting to import the module that was just built. I'm hoping for something subtler though; I wonder if there's an identifyable point where the lib directory got created. -- --Guido van Rossum (home page: http://www.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] assertRaises
On Thu, Jul 17, 2008 at 2:54 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote: > > I said: >> Let's just make assertRaises return the exception instance, it seems like it >> feels the need correctly. > > and I meant "fills", not "feels", obviously... +1 : enriching the existing method in a way that's perfectly transparent and innocuous to all existing uses _feels_ right, because it's more practical. Alex ___ 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-3000] No beta2 tonight
On Thu, Jul 17, 2008 at 10:07 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 6:16 AM, Jesse Noller <[EMAIL PROTECTED]> wrote: >> 3375: Guido (thanks guido) looked into this, and while I banged my >> head on it a lot yesterday - guido's identified the issue, and now I >> need to figure out a fix - help is welcome on this one. > > You're welcome. I would have never found this if I hadn't had a > heightened awareness of the sys.path_importer_cache variable recently, > due to implementing a zipimport.py for Google App Engine. :-) > > I can try looking for a fix later today (in a few hours). A very crude > fix would be to just remove all keys that have NullImporter values > from that variable just before attempting to import the module that > was just built. I'm hoping for something subtler though; I wonder if > there's an identifyable point where the lib directory got created. > An additional note for anyone else - this is only under py3k - trunk is perfectly fine. ___ 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] No beta2 tonight
On Wed, Jul 16, 2008 at 11:30 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We have green buildbots, yay! Thanks everyone for that. The Windows buildbots are not very happy, though. test_ssl and test_bsddb and constantly failing on both the trunk and py3k. I don't know much about either of these items (or Windows for that matter), so any help would be greatly appreciated. -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1." ___ 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] PEP 3101: floats format 'f' and 'F'
Eric Smith wrote:
Guido van Rossum wrote:
It shares code with %-formatting. Change that, too? I couldn't find
any
occurrences of %F in the stdlib. Not that that's the entire
universe, of
course.
The change is slightly less elegant if I don't change %-formatting, but
still doable, especially if the betas don't get cut today.
Fine with me to change %F as well -- after all that's where the
misunderstanding comes from. (More and more I'm beginning to think it
was my mistake. :-)
I added this as
http://mail.python.org/pipermail/python-dev/2008-July/081242.html
I should be able to get it checked in today.
I have this ready for checkin (with docs and tests). I'd like to get it
in for this beta, since it does involved changed behavior, no matter how
small ('1e+100' becomes '1E+100' with '%F'). But it relies on the
platform's vsnprintf to do the right thing with 'F', so I'm worried
about breakages on platforms I don't have access to. Resolving those
issues might take a few days.
Any advice on checking this in now, or waiting until after this beta is
released?
On a related note, I've wanted to clean up float formatting for ages.
The test:
if ((type == 'f' || type == 'F') && (fabs(x) / 1e25) >= 1e25)
is in the code in 3 places, for example. I'm hoping I can get to that
project, but since it won't change functionality I can do it later.
Eric.
___
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] Unittest PEP do's and don'ts (BDFL pronouncement)
Nick Coghlan wrote: Taking an existing function such as assertRaises and going "hey, we aren't using the return value from this, wouldn't it be really convenient if it told us the exact exception it actually caught?" doesn't cause any problems for existing code, and makes it much easier to write tests that need to check additional details about the exception that is raised (e.g. to check that the correct error code is captured and reported for things like OSError). The essence of the function remains unchanged - you're still asserting that a particular exception is raised. Returning the actual exception object that was caught is merely a convenience that makes a lot of sense. I'm not sure I understand... If "a particular exception is raised", every thing is good and there is no error to report. ie... the code being tested did the right thing. If it does not raise the particular desired exception, isn't either a failureException raised or someother exception, which is caught by the unittest test runner. In that case the assertRaises method never gets a chance to return anything. If this is correct, then the exception needs to be caught and passed out via the failureException, and not the returned value. Ron ___ 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] PEP 3101: floats format 'f' and 'F'
From: "Eric Smith" <[EMAIL PROTECTED]>
I have this ready for checkin (with docs and tests). I'd like to get it
in for this beta, since it does involved changed behavior, no matter how
small ('1e+100' becomes '1E+100' with '%F'). But it relies on the
platform's vsnprintf to do the right thing with 'F', so I'm worried
about breakages on platforms I don't have access to. Resolving those
issues might take a few days.
Any advice on checking this in now, or waiting until after this beta is
released?
I recommend doing it after the release. It's unlikely to be exercised
much by the beta users so there's no real advantage. If you wait
until afterwards, then there is time to let the buildbots have a go
at it and reveal any cross-platform issues.
Besides, Barry said something about getting meaner.
Would hate to find out what he meant the hard way ;-)
Raymond
___
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-3000] No beta2 tonight
On Thu, Jul 17, 2008 at 8:36 AM, Jesse Noller <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 10:07 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: >> On Thu, Jul 17, 2008 at 6:16 AM, Jesse Noller <[EMAIL PROTECTED]> wrote: >>> 3375: Guido (thanks guido) looked into this, and while I banged my >>> head on it a lot yesterday - guido's identified the issue, and now I >>> need to figure out a fix - help is welcome on this one. >> >> You're welcome. I would have never found this if I hadn't had a >> heightened awareness of the sys.path_importer_cache variable recently, >> due to implementing a zipimport.py for Google App Engine. :-) >> >> I can try looking for a fix later today (in a few hours). A very crude >> fix would be to just remove all keys that have NullImporter values >> from that variable just before attempting to import the module that >> was just built. I'm hoping for something subtler though; I wonder if >> there's an identifyable point where the lib directory got created. I submitted a fix along these lines -- other things I tried did not work out. The issue is fixed. > An additional note for anyone else - this is only under py3k - trunk > is perfectly fine. Right. I'm thinking that something changed in the massaging of the default search path, but I can't be bothered to investigate further. I do know that right after startup there are more non-trivial entries in sys.path_importer_cache in 3.0 than there are in 2.6. -- --Guido van Rossum (home page: http://www.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] PEP 3101: floats format 'f' and 'F'
On Thu, Jul 17, 2008 at 9:25 AM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> From: "Eric Smith" <[EMAIL PROTECTED]>
>>
>> I have this ready for checkin (with docs and tests). I'd like to get it
>> in for this beta, since it does involved changed behavior, no matter how
>> small ('1e+100' becomes '1E+100' with '%F'). But it relies on the
>> platform's vsnprintf to do the right thing with 'F', so I'm worried
>> about breakages on platforms I don't have access to. Resolving those
>> issues might take a few days.
>>
>> Any advice on checking this in now, or waiting until after this beta is
>> released?
>
> I recommend doing it after the release. It's unlikely to be exercised
> much by the beta users so there's no real advantage. If you wait
> until afterwards, then there is time to let the buildbots have a go
> at it and reveal any cross-platform issues.
>
> Besides, Barry said something about getting meaner.
> Would hate to find out what he meant the hard way ;-)
I'd advise the opposite -- check it in now. It's not going to break
anything, and if it is, let's find out sooner rather than later.
--
--Guido van Rossum (home page: http://www.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] No beta2 tonight
> test_ssl ... constantly failing on both the trunk and py3k. I'll take a closer look at this. It's the new test added in lately. Seems to be working on non-Windows platforms, so I'm guessing it's some Windows oddity, which I'm not very good at diagnosing. Worst comes to worst, we can take out that test. Bill ___ 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] Unittest PEP do's and don'ts (BDFL pronouncement)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ron Adam wrote: > > Nick Coghlan wrote: >> The essence of the function remains unchanged - you're still asserting >> that a particular exception is raised. Returning the actual exception >> object that was caught is merely a convenience that makes a lot of sense. > > I'm not sure I understand... > > If "a particular exception is raised", every thing is good and there is no > error to report. ie... the code being tested did the right thing. I *think* that in this case the propoent wants to be able to make further assertions about the raised exception (e.g., to test its message). Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIf3+T+gerLs4ltQ4RAk/VAKCK8hnX2C7DE57RSxA88THttT5tSwCg2taQ zzRkJ/SEPwZvgfcluo2DTvw= =KTGx -END PGP SIGNATURE- ___ 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] Unittest PEP do's and don'ts (BDFL pronouncement)
Please move all discussions of unittest frameworks to [EMAIL PROTECTED] It is an interesting topic -- so interesting, in fact, that exploring all the different ideas under discussion is overwhelming the primary purpose of python-dev, which at this point is to get the 2.6 and 3.0 releases into shape. -- --Guido van Rossum (home page: http://www.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] [Python-3000] No beta2 tonight
> > test_ssl ... constantly failing on both the trunk and py3k.
>
> I'll take a closer look at this. It's the new test added in lately.
> Seems to be working on non-Windows platforms, so I'm guessing it's
> some Windows oddity, which I'm not very good at diagnosing. Worst
> comes to worst, we can take out that test.
It looks like the handshake code in _ssl.c is returning this Windows
error (I'm looking at the trunk):
ERROR: testWrongCert (test.test_ssl.ThreadedTests)
--
Traceback (most recent call last):
File
"E:\cygwin\home\db3l\buildarea\trunk.bolen-windows\build\lib\test\test_ssl.py",
line 807, in testWrongCert
"wrongcert.pem"))
File
"E:\cygwin\home\db3l\buildarea\trunk.bolen-windows\build\lib\test\test_ssl.py",
line 597, in badCertTest
s.connect((HOST, server.port))
File "E:\cygwin\home\db3l\buildarea\trunk.bolen-windows\build\lib\ssl.py",
line 272, in connect
self.do_handshake()
File "E:\cygwin\home\db3l\buildarea\trunk.bolen-windows\build\lib\ssl.py",
line 256, in do_handshake
self._sslobj.do_handshake()
error: [Errno 10054] An existing connection was forcibly closed by the remote
host
Error 10054 is WSAECONNRESET, according to Google.
Arguably, it's an error in this scrap of _ssl.c:
} else if (ret == -1) {
/* underlying BIO reported an I/O error */
return obj->Socket->errorhandler();
}
I should be checking for EOF error returns like this one from Socket,
and returning an PY_SSL_ERROR_EOF exception. Is there a list somewhere
of what EOF errors are signalled by Socket?
Bill
___
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] No beta2 tonight
On Thu, Jul 17, 2008 at 9:16 AM, Jesse Noller <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 12:30 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> We have green buildbots, yay! Thanks everyone for that. >> >> However, we still have three release blocker issues that I am not >> comfortable deferring. >> >> 3088 test_multiprocessing hangs intermittently on POSIX platforms >> 3375 _multiprocessing.so build problems >> 874900 threading module can deadlock after fork >> >> My biggest concern is 3375 and 3088, the latter has a dependency on 874900. >> >> 3375 is very strange since a subsequent 'make' completes just fine. This >> issue happens for me on both OS X 10.5 and Ubuntu 8.04 for py3k. >> >> 3088 does not appear to be happening now on OS X or Ubuntu, but the issue >> (and its dependent issue) are not closed, so I'm not sure exactly what's >> going on here. >> >> So we'll give these releases another 24 hours. Please, if you have time see >> what you can do about resolving these three blockers. Chat with me on >> #python-dev if you think we should release anyway. I will try to look into >> 3375, but I'd like to know if anybody else is seeing these build failures. >> >> I'll note that I plan to hold the beta3 releases until all release blocker >> and deferred blockers are resolved. >> >> - -Barry >> > > Quick status update, since I'm the gating factor. > > 3088: I didn't want to close this until 874900's patch was submitted, > ported to py3k and I saw green build bots. By the time I went to sleep > last night, we were still seeing 2to3 test timeouts on the build bots. > I will port the patch to 3k today and lower the priority of 874900 and > close 3088 shortly. > > 3375: Guido (thanks guido) looked into this, and while I banged my > head on it a lot yesterday - guido's identified the issue, and now I > need to figure out a fix - help is welcome on this one. > > I apologize for not getting these resolved last night > > -jesse > Just to close the loop - 3088 is closed now, and 874900 is on py3k, therefore lowered from a release blocker for now (it needs to remain open to finish resolving a few issues) Guido fixed 3375 (thanks again) -jesse ___ 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
[Python-Dev] Implementing restricted Python in Zope2
I have taken the gsoc 08 project of porting zope2 to python2.5. Through my way to the successful completion of the project I have to implement Restricted python in Zope2. I could only get the information that the python AST has not changed on moving from python2.4 to 2.5 but Restricted Python is not well documented enough for a stident to test the Zope2 's Restricted Python implentation. As a student I am not familiar with Restricted Python and python AST implementation.And in need of help to start the Restricted Python implementation. Ranjith. ___ 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] No beta2 tonight
> The Windows buildbots are not very happy, though. test_ssl ... > constantly failing on both the trunk and py3k. I've checked in patches for test_ssl on both branches. Let's see how the Windows buildbots do. Bill ___ 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] Implementing restricted Python in Zope2
On Thu, Jul 17, 2008 at 10:54 AM, ranjith kannikara <[EMAIL PROTECTED]> wrote: > I have taken the gsoc 08 project of porting zope2 to python2.5. > Through my way to the successful completion of the project I have to > implement Restricted python in Zope2. I could only get the information > that the python AST has not changed on moving from python2.4 to 2.5 > but Restricted Python is not well documented enough for a stident to > test the Zope2 's Restricted Python implentation. > > As a student I am not familiar with Restricted Python and python AST > implementation.And in need of help to start the Restricted Python > implementation. > What do you mean, "Restricted Python"? If you mean rexec and Bastion, they are no longer supported, and that began before 2.5. -Brett ___ 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] Implementing restricted Python in Zope2
On Thu, Jul 17, 2008 at 11:27 AM, Brett Cannon <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 10:54 AM, ranjith kannikara > <[EMAIL PROTECTED]> wrote: >> I have taken the gsoc 08 project of porting zope2 to python2.5. >> Through my way to the successful completion of the project I have to >> implement Restricted python in Zope2. I could only get the information >> that the python AST has not changed on moving from python2.4 to 2.5 >> but Restricted Python is not well documented enough for a stident to >> test the Zope2 's Restricted Python implentation. >> >> As a student I am not familiar with Restricted Python and python AST >> implementation.And in need of help to start the Restricted Python >> implementation. > What do you mean, "Restricted Python"? If you mean rexec and Bastion, > they are no longer supported, and that began before 2.5. Maybe he's talking about PyPy's RPython, which is notoriously (and it seems intentionally) underspecified? In that case, please contact the PyPy team. Or maybe there is something in Zope 2 called Restricted Python -- in that case please contact the Zope lists. There's nothing in the collective memory of python-dev called Restricted Python that we can help you with. -- --Guido van Rossum (home page: http://www.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] PEP 3101: floats format 'f' and 'F'
Guido van Rossum schrieb:
> On Thu, Jul 17, 2008 at 9:25 AM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
>> From: "Eric Smith" <[EMAIL PROTECTED]>
>>>
>>> I have this ready for checkin (with docs and tests). I'd like to get it
>>> in for this beta, since it does involved changed behavior, no matter how
>>> small ('1e+100' becomes '1E+100' with '%F'). But it relies on the
>>> platform's vsnprintf to do the right thing with 'F', so I'm worried
>>> about breakages on platforms I don't have access to. Resolving those
>>> issues might take a few days.
>>>
>>> Any advice on checking this in now, or waiting until after this beta is
>>> released?
>>
>> I recommend doing it after the release. It's unlikely to be exercised
>> much by the beta users so there's no real advantage. If you wait
>> until afterwards, then there is time to let the buildbots have a go
>> at it and reveal any cross-platform issues.
>>
>> Besides, Barry said something about getting meaner.
>> Would hate to find out what he meant the hard way ;-)
>
> I'd advise the opposite -- check it in now. It's not going to break
> anything, and if it is, let's find out sooner rather than later.
>
Before we get old waiting for the windows buildbots, here how test_format
fails now (on XP SP2 x86, trunk rev 65072:
c:\svn\trunk\PCbuild>.\\python_d -E -tt ../lib/test/regrtest.py test_format
test_format
test test_format produced unexpected output:
**
'%F' % (1.0,) == '' != '1.00'
u'%F' % (1.0,) == u'' != '1.00'
'%f' % (nan,) == '-1.#IND00' != 'nan'
u'%f' % (nan,) == u'-1.#IND00' != 'nan'
'%F' % (nan,) == '' != 'NAN'
u'%F' % (nan,) == u'' != 'NAN'
'%f' % (inf,) == '1.#INF' != 'inf'
u'%f' % (inf,) == u'1.#INF' != 'inf'
'%F' % (inf,) == '1.#INF' != 'INF'
u'%F' % (inf,) == u'1.#INF' != 'INF'
**
1 test failed:
test_format
[23521 refs]
c:\svn\trunk\PCbuild>
Windows vsnprintf does not support '%F' at all, and '%f' does not
behave as expected with nan and inf.
--
Thanks,
Thomas
___
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] PEP 3101: floats format 'f' and 'F'
Thomas Heller wrote:
Guido van Rossum schrieb:
On Thu, Jul 17, 2008 at 9:25 AM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
From: "Eric Smith" <[EMAIL PROTECTED]>
I have this ready for checkin (with docs and tests). I'd like to get it
in for this beta, since it does involved changed behavior, no matter how
small ('1e+100' becomes '1E+100' with '%F'). But it relies on the
platform's vsnprintf to do the right thing with 'F', so I'm worried
about breakages on platforms I don't have access to. Resolving those
issues might take a few days.
Any advice on checking this in now, or waiting until after this beta is
released?
I recommend doing it after the release. It's unlikely to be exercised
much by the beta users so there's no real advantage. If you wait
until afterwards, then there is time to let the buildbots have a go
at it and reveal any cross-platform issues.
Besides, Barry said something about getting meaner.
Would hate to find out what he meant the hard way ;-)
I'd advise the opposite -- check it in now. It's not going to break
anything, and if it is, let's find out sooner rather than later.
Before we get old waiting for the windows buildbots, here how test_format
fails now (on XP SP2 x86, trunk rev 65072:
c:\svn\trunk\PCbuild>.\\python_d -E -tt ../lib/test/regrtest.py test_format
test_format
test test_format produced unexpected output:
**
'%F' % (1.0,) == '' != '1.00'
u'%F' % (1.0,) == u'' != '1.00'
'%f' % (nan,) == '-1.#IND00' != 'nan'
u'%f' % (nan,) == u'-1.#IND00' != 'nan'
'%F' % (nan,) == '' != 'NAN'
u'%F' % (nan,) == u'' != 'NAN'
'%f' % (inf,) == '1.#INF' != 'inf'
u'%f' % (inf,) == u'1.#INF' != 'inf'
'%F' % (inf,) == '1.#INF' != 'INF'
u'%F' % (inf,) == u'1.#INF' != 'INF'
**
1 test failed:
test_format
[23521 refs]
c:\svn\trunk\PCbuild>
Windows vsnprintf does not support '%F' at all, and '%f' does not
behave as expected with nan and inf.
I was afraid of that. I'll back these out until I can dig up a Windows
box to test on.
Thanks for checking this.
Eric.
___
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
[Python-Dev] Issue2944: need a review
Can anyone look at the patch for Issue2944? I hope the issue can be fixed before the release of python 2.6. ___ 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] Implementing restricted Python in Zope2
At 11:27 AM 7/17/2008 -0700, Brett Cannon wrote: On Thu, Jul 17, 2008 at 10:54 AM, ranjith kannikara <[EMAIL PROTECTED]> wrote: > I have taken the gsoc 08 project of porting zope2 to python2.5. > Through my way to the successful completion of the project I have to > implement Restricted python in Zope2. I could only get the information > that the python AST has not changed on moving from python2.4 to 2.5 > but Restricted Python is not well documented enough for a stident to > test the Zope2 's Restricted Python implentation. > > As a student I am not familiar with Restricted Python and python AST > implementation.And in need of help to start the Restricted Python > implementation. > What do you mean, "Restricted Python"? If you mean rexec and Bastion, they are no longer supported, and that began before 2.5. No, he means the restricted Python compiler and capability-proxy system used by Zope. You know, the one I always bring up whenever anybody says they want to implement capabilities in Python? ;-) Zope's restricted Python is basically a combination of a special compiler, __builtin__ replacements, and a proxy type. Instead of using LOAD_ATTR opcodes, the compiler generates code that calls a special getattr() function instead, and most objects other than relatively-safe builtin types are wrapped in proxies that control what attributes can be accessed and what operations can be performed. The restricted Python framework itself doesn't impose any particular security policy; proxies delegate checks to "checker" objects that are essentially capabilities. Mostly, it focuses on creating a safe sandbox that can be expanded. There are two parts to the implication; one is called RestrictedPython and lives at: http://svn.zope.org/RestrictedPython/trunk The other part is "zope.security.untrustedpython", and it's part of the zope.security distribution; see: http://svn.zope.org/zope.security/trunk/src/zope/security/untrustedpython/ for its specific code and docs. Both packages appear to have automated tests. ___ 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] Issue2944: need a review
Suggestion for people asking developers to look into issues: indicate more than the issue number in the email. Show the issue summary, other relevant metadata, and what needs to be done in some detail. This will pique the interest of those who *can* help (and allow people who can't help anyway to skip the message more efficiently). On Thu, Jul 17, 2008 at 12:41 PM, Alexander Shigin <[EMAIL PROTECTED]> wrote: > Can anyone look at the patch for Issue2944? > > I hope the issue can be fixed before the release of python 2.6. -- --Guido van Rossum (home page: http://www.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] Implementing restricted Python in Zope2
Thanks. Then python-dev is *definitely* the wrong forum. :-) On Thu, Jul 17, 2008 at 1:26 PM, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > At 11:27 AM 7/17/2008 -0700, Brett Cannon wrote: >> >> On Thu, Jul 17, 2008 at 10:54 AM, ranjith kannikara >> <[EMAIL PROTECTED]> wrote: >> > I have taken the gsoc 08 project of porting zope2 to python2.5. >> > Through my way to the successful completion of the project I have to >> > implement Restricted python in Zope2. I could only get the information >> > that the python AST has not changed on moving from python2.4 to 2.5 >> > but Restricted Python is not well documented enough for a stident to >> > test the Zope2 's Restricted Python implentation. >> > >> > As a student I am not familiar with Restricted Python and python AST >> > implementation.And in need of help to start the Restricted Python >> > implementation. >> > >> >> What do you mean, "Restricted Python"? If you mean rexec and Bastion, >> they are no longer supported, and that began before 2.5. > > No, he means the restricted Python compiler and capability-proxy system used > by Zope. You know, the one I always bring up whenever anybody says they > want to implement capabilities in Python? ;-) > > Zope's restricted Python is basically a combination of a special compiler, > __builtin__ replacements, and a proxy type. Instead of using LOAD_ATTR > opcodes, the compiler generates code that calls a special getattr() function > instead, and most objects other than relatively-safe builtin types are > wrapped in proxies that control what attributes can be accessed and what > operations can be performed. > > The restricted Python framework itself doesn't impose any particular > security policy; proxies delegate checks to "checker" objects that are > essentially capabilities. Mostly, it focuses on creating a safe sandbox > that can be expanded. > > There are two parts to the implication; one is called RestrictedPython and > lives at: > > http://svn.zope.org/RestrictedPython/trunk > > The other part is "zope.security.untrustedpython", and it's part of the > zope.security distribution; see: > > http://svn.zope.org/zope.security/trunk/src/zope/security/untrustedpython/ > > for its specific code and docs. > > Both packages appear to have automated tests. > > ___ > 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 (home page: http://www.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] Issue2944: need a review
These requests always have a higher probability of being addressed if you summarize the issue in the request. Bill > Can anyone look at the patch for Issue2944? > > I hope the issue can be fixed before the release of python 2.6. ___ 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] Implementing restricted Python in Zope2
On Thu, Jul 17, 2008 at 6:04 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > Thanks. Then python-dev is *definitely* the wrong forum. :-) Definitely wrong forum for RestrictedPython-specifc questions, but not if you consider those two paragraphs from Shane's email, which clarify that Ranjith is seeking for information on possible AST changes that might have occurred in Python 2.5: """ The safety of RestrictedPython has been validated in a somewhat formal process with Python 2.4. Ranjith is working to validate it with Python 2.5. He is first working to discover all changes between Python 2.4 and 2.5 that might have affected the safety of a RestrictedPython sandbox. Any changes to the AST, builtin functions, methods of builtin types, etc., need to be evaluated for safety. So, in general, he is looking for detailed lists of changes between Python 2.4 and 2.5--more than the "What's New" doc. """ -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Implementing restricted Python in Zope2
On Thu, Jul 17, 2008 at 4:10 PM, Sidnei da Silva <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 6:04 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: >> Thanks. Then python-dev is *definitely* the wrong forum. :-) > > Definitely wrong forum for RestrictedPython-specifc questions, but not > if you consider those two paragraphs from Shane's email, which clarify > that Ranjith is seeking for information on possible AST changes that > might have occurred in Python 2.5: > > """ > The safety of RestrictedPython has been validated in a somewhat formal > process with Python 2.4. Ranjith is working to validate it with > Python 2.5. He is first working to discover all changes between > Python 2.4 and 2.5 that might have affected the safety of a > RestrictedPython sandbox. Any changes to the AST, builtin functions, > methods of builtin types, etc., need to be evaluated for safety. > > So, in general, he is looking for detailed lists of changes between > Python 2.4 and 2.5--more than the "What's New" doc. > """ Then I would recommend he look at Misc/NEWS. If he needs more information, *specific* questions will bring the best results. -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1." ___ 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] Implementing restricted Python in Zope2
Benjamin Peterson wrote: On Thu, Jul 17, 2008 at 4:10 PM, Sidnei da Silva <[EMAIL PROTECTED]> wrote: """ The safety of RestrictedPython has been validated in a somewhat formal process with Python 2.4. Ranjith is working to validate it with Python 2.5. He is first working to discover all changes between Python 2.4 and 2.5 that might have affected the safety of a RestrictedPython sandbox. Any changes to the AST, builtin functions, methods of builtin types, etc., need to be evaluated for safety. So, in general, he is looking for detailed lists of changes between Python 2.4 and 2.5--more than the "What's New" doc. """ Then I would recommend he look at Misc/NEWS. If he needs more information, *specific* questions will bring the best results. Ultimately, he can do a diff of the corresponding C files, and read the checkin messages that hopefully explain some of the changes. ___ 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] Unittest PEP do's and don'ts (BDFL pronouncement)
Tres Seaver wrote: Ron Adam wrote: Nick Coghlan wrote: The essence of the function remains unchanged - you're still asserting that a particular exception is raised. Returning the actual exception object that was caught is merely a convenience that makes a lot of sense. I'm not sure I understand... If "a particular exception is raised", every thing is good and there is no error to report. ie... the code being tested did the right thing. I *think* that in this case the propoent wants to be able to make further assertions about the raised exception (e.g., to test its message). Exactly. Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.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] Issue2944: need a review
Guido van Rossum wrote: Suggestion for people asking developers to look into issues: indicate more than the issue number in the email. Show the issue summary, other relevant metadata, and what needs to be done in some detail. This will pique the interest of those who *can* help (and allow people who can't help anyway to skip the message more efficiently). Links of the form http://bugs.python.org/issue2944 don't hurt either :) That particular issue is an asyncore problem, so I cc'ed Josiah directly on this message. Cheers, Nick. On Thu, Jul 17, 2008 at 12:41 PM, Alexander Shigin <[EMAIL PROTECTED]> wrote: Can anyone look at the patch for Issue2944? I hope the issue can be fixed before the release of python 2.6. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.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] assertRaises
> >> Let's just make assertRaises return the exception instance, it seems > >> like it feels the need correctly. > > > > and I meant "fills", not "feels", obviously... > > +1 : enriching the existing method in a way that's perfectly > transparent and innocuous to all existing uses _feels_ right, because > it's more practical. For the record, and primarily to give the champion of this proposal a little more resolve the run the python-dev gauntlet on this issue given the recent - err - spirited discussions, I'm also strongly +1 on this idea. Cheers, Mark ___ 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] No beta2 tonight
> The Windows buildbots are not very happy, though. test_ssl and > test_bsddb and constantly failing on both the trunk and py3k. I don't > know much about either of these items (or Windows for that matter), so > any help would be greatly appreciated. bsddb is in a very bad shape, as the 2.6 code hasn't been merged into 3k. I somewhat doubt that this gets resolved before the release, so bsddb users might need to skip 3.0. Regards, Martin ___ 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] No beta2 tonight
On Thu, Jul 17, 2008 at 6:27 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: >> The Windows buildbots are not very happy, though. test_ssl and >> test_bsddb and constantly failing on both the trunk and py3k. I don't >> know much about either of these items (or Windows for that matter), so >> any help would be greatly appreciated. > > bsddb is in a very bad shape, as the 2.6 code hasn't been merged into > 3k. I somewhat doubt that this gets resolved before the release, so > bsddb users might need to skip 3.0. Ok. ssl has stopped failing now (Thanks Bill). test_wsgiref is failing on the trunk, but as it is an externally maintained module, there isn't much I can do about it. (see issue #3401). Overall, though, I think we've done what we can here, so these shouldn't hold up the release. > > Regards, > Martin > -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1." ___ 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] No beta2 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 18, 2008, at 01:27 AM, Martin v. Löwis wrote: >> The Windows buildbots are not very happy, though. test_ssl and >> test_bsddb and constantly failing on both the trunk and py3k. I don't >> know much about either of these items (or Windows for that matter), so >> any help would be greatly appreciated. > >bsddb is in a very bad shape, as the 2.6 code hasn't been merged into >3k. I somewhat doubt that this gets resolved before the release, so >bsddb users might need to skip 3.0. We have no showstoppers and several green buildbots, so I'm going to make the releases tonight. Please, NO CHECKINS until I say so, or ping me on #python-dev. As for bsddb, we'll make a determination after beta3. If it's terminally busted for Python 3.0, so be it. Thanks everyone for working so hard at getting beta2 ready. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIf/xT2YZpQepbvXERAtmoAKCyUkejAFxFG10Bsn/CJjZfGy0B9QCeMO0z momJmXRLCdmxs84j2hXGrTY= =Y3wS -END PGP SIGNATURE- ___ 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] No beta2 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 17, 2008, at 09:57 AM, Steve Holden wrote: >Barry Warsaw wrote: >[...] >> >> I'll note that I plan to hold the beta3 releases until all release >> blocker and deferred blockers are resolved. >> >Ian Ozsvald of ShowMeDo.com noticed a blog post of mine about this beta, >and responded as follows: > >> Re. >> http://holdenweb.blogspot.com/2008/07/cpython-getting-serious-about-quality.html >> If someone on the dev side wanted to make a 5-10 minute 'cast on how to >> check out the python base, build it, test it, check stuff back in, we'd be >> honoured to host it. Obviously the entire process deserves more attention >> but a short overview pointing out the key steps would be: >> 1) simple for the author to create >> 2) easy for possible contributors to watch and receive inspiration >> 3) powerful enough to attract another set of developers into the fold >> so that might be a useful, low-cost, quick win to help with the current >> effort? > >I'd do this myself but a) I'm not the obvious candidate and b) I'm too >busy to give it my attention now. > >If someone wanted to tackle this, it might help getting people testing >for the next beta, and also to recruit more testers in the long-term. It's a great idea, but unfortunately I also don't have time to do this right now. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIf/0G2YZpQepbvXERAtNzAJ9Os117wAD8KCkhkt6x+jhKuJ4snwCfbjXS VtkFGzUUTzg+ersqU3+TObg= =jdUf -END PGP SIGNATURE- ___ 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] No beta2 tonight
On Jul 17, 2008, at 7:27 PM, Martin v. Löwis wrote: bsddb is in a very bad shape, as the 2.6 code hasn't been merged into 3k. I somewhat doubt that this gets resolved before the release, so bsddb users might need to skip 3.0. In fact, bsddb as packages in core Python has rarely been in good shape. Has anyone actually considered that bsddb might do better if maintained strictly as an external package? That would make it easier for the any maintainers to release updates, and removes a source of frustration for users who either don't need it or would rather wait for a happier version. I think this is worth considering. I vaguely recall that the bsddb module was maintained before it was incorporated into the core Python release. -Fred -- Fred Drake ___ 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-3000] No beta2 tonight
On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake <[EMAIL PROTECTED]> wrote: > On Jul 17, 2008, at 7:27 PM, Martin v. Löwis wrote: >> >> bsddb is in a very bad shape, as the 2.6 code hasn't been merged into >> 3k. I somewhat doubt that this gets resolved before the release, so >> bsddb users might need to skip 3.0. > > > In fact, bsddb as packages in core Python has rarely been in good shape. > > Has anyone actually considered that bsddb might do better if maintained > strictly as an external package? That would make it easier for the any > maintainers to release updates, and removes a source of frustration for > users who either don't need it or would rather wait for a happier version. > > I think this is worth considering. I vaguely recall that the bsddb module > was maintained before it was incorporated into the core Python release. +1. In my recollection maintaining bsddb has been nothing but trouble right from the start when we were all sitting together at "Zope Corp North" in a rented office in McLean... We can remove it from 3.0. We can't really remove it from 2.6, but we can certainly start end-of-lifing it in 2.6. -- --Guido van Rossum (home page: http://www.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] Implementing restricted Python in Zope2
Hi , I am really sorry that I couldn,t make clear in the first mail that What I actually need. But Shane and my Gsoc mentor Sidnei have already made it clear I think. I would like to know how much the AST have been changed on moving from python2.4 to python 2.5 so that I can bring the corresponding changes in Zope2 to get it adapted to those changes in the AST. Also the changes that have come to the builtin function and so which should have affected the safety of a RestrictedPython sandbox. As Shane have told a detailed list of such changes can help me than the "Whats New" doc... Ranjith. On Fri, Jul 18, 2008 at 2:43 AM, Benjamin Peterson <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 4:10 PM, Sidnei da Silva > <[EMAIL PROTECTED]> wrote: >> On Thu, Jul 17, 2008 at 6:04 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: >>> Thanks. Then python-dev is *definitely* the wrong forum. :-) >> >> Definitely wrong forum for RestrictedPython-specifc questions, but not >> if you consider those two paragraphs from Shane's email, which clarify >> that Ranjith is seeking for information on possible AST changes that >> might have occurred in Python 2.5: >> >> """ >> The safety of RestrictedPython has been validated in a somewhat formal >> process with Python 2.4. Ranjith is working to validate it with >> Python 2.5. He is first working to discover all changes between >> Python 2.4 and 2.5 that might have affected the safety of a >> RestrictedPython sandbox. Any changes to the AST, builtin functions, >> methods of builtin types, etc., need to be evaluated for safety. >> >> So, in general, he is looking for detailed lists of changes between >> Python 2.4 and 2.5--more than the "What's New" doc. >> """ > > Then I would recommend he look at Misc/NEWS. If he needs more > information, *specific* questions will bring the best results. > > > > -- > Cheers, > Benjamin Peterson > "There's no place like 127.0.0.1." > ___ 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
[Python-Dev] NO CHECKINS - BETA 2 COMING
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please, no checkins on the 3.0 or 2.6 branches until further notice. We're a go with the releases tonight. Email is not the quickest way to get my attention. For that, use irc on freenode, #python-dev. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSIAFGnEjvBPtnXfVAQIBmwP/VzIYu58DzSND0CNM0NKfsWVS9yTnBVi8 EijaxenUv0rRVloCawJbK8cMOyI0JmEa4GE5bMrCf+o9niRgFeJxrYEaw1jN4fWW dsXH8Fuw/nHpoUnFDbu5ePaBdvcOSuWKTS/iGq2i9DzfYXdx+FaXqZ/mhx43bY3o eCF7I+y/fPg= =iTgT -END PGP SIGNATURE- ___ 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-3000] No beta2 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 17, 2008, at 10:37 PM, Guido van Rossum wrote: On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake <[EMAIL PROTECTED]> wrote: On Jul 17, 2008, at 7:27 PM, Martin v. Löwis wrote: bsddb is in a very bad shape, as the 2.6 code hasn't been merged into 3k. I somewhat doubt that this gets resolved before the release, so bsddb users might need to skip 3.0. In fact, bsddb as packages in core Python has rarely been in good shape. Has anyone actually considered that bsddb might do better if maintained strictly as an external package? That would make it easier for the any maintainers to release updates, and removes a source of frustration for users who either don't need it or would rather wait for a happier version. I think this is worth considering. I vaguely recall that the bsddb module was maintained before it was incorporated into the core Python release. +1. In my recollection maintaining bsddb has been nothing but trouble right from the start when we were all sitting together at "Zope Corp North" in a rented office in McLean... We can remove it from 3.0. We can't really remove it from 2.6, but we can certainly start end-of-lifing it in 2.6. +1, but please, after I make tonight's releases. :) - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSIAFenEjvBPtnXfVAQKEewP+OWCBAH437X4+EptdcuIFFYrCCVXqbrV4 F2dZMyv/RU0jYgd6YTLspklEIzuEcH1sxYsnh2q4aWNfFlfL50LPf1/TKurZpO2C 9CrjEZpTcK0k5z5FCxAOLdVFLQDC4w7FGYop3uR27g5u9KCLdQvTrPs/mZllv263 /g2YdwhZFEE= =NAOe -END PGP SIGNATURE- ___ 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
[Python-Dev] RELEASED Python 2.6b2 and 3.0b2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On behalf of the Python development team and the Python community, I am happy to announce the second beta releases of Python 2.6 and Python 3.0. Please note that these are beta releases, and as such are not suitable for production environments. We continue to strive for a high degree of quality, and these releases are intended to freeze the feature set for Python 2.6 and 3.0. From now until the planned final releases in October 2008, we will be fixing known problems and stabilizing these new Python versions. You can help by downloading and testing them, providing feedback and hopefully helping to fix bugs. You can also use these releases to determine how changes in 2.6 and 3.0 might impact you. ONLY ONE MORE BETA RELEASE IS PLANNED, so now is a great time to download the releases and try them with your code. If you find things broken or incorrect, please submit bug reports at http://bugs.python.org For more information and downloadable distributions, see the Python 2.6 website: http://www.python.org/download/releases/2.6/ and the Python 3.0 web site: http://www.python.org/download/releases/3.0/ See PEP 361 for release schedule details: http://www.python.org/dev/peps/pep-0361/ Enjoy, - -Barry Barry Warsaw [EMAIL PROTECTED] Python 2.6/3.0 Release Manager (on behalf of the entire python-dev team) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSIARKHEjvBPtnXfVAQL7AQQAjPSbfKz2Oh/au/hPzS4x2IR5/R6FVe+g o9UYrONNRKJ14UHpbZRzvIvw/4G3PdpzzGxjYFIhVGEesEGJnMzT3YdkMHt4NW9d HOZxL3hseGbTdpUJPCsIkNG+4hX7iuY3NSV81Z75LGAL4tqbooGqwwUslXMT5f8s lRrZUcBRKZ0= =ju6s -END PGP SIGNATURE- ___ 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
[Python-Dev] SVN IS OPEN
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The releases have been made, so both the 3.0 branch and the trunk (2.6) are now open for commits. Remember, there's only one more planned beta, and we /really/ want to try to hit the October 1st deadline. Let's do everything we can to stabilize these releases, address the blockers, and turn those buildbots green. Thanks everyone. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSIATAHEjvBPtnXfVAQIWLAP+OVUXh3H5j8WN4cm3fHcLkgd+E4FuWWwb zKr7JPYUHhgvwpYB5iZjQuJe/62qKXh70wNWyDcxLi9/TEbx8NvhQ+nMbHAJkfE2 1/HkP9bbgiwE/JYJsN0a0DK/MSpwvxfxxakQrQV9H8SiL5aDqlVCFdzLu31SkOhx iQ+iTCqwIdY= =UOPo -END PGP SIGNATURE- ___ 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] SVN IS OPEN
On Thu, Jul 17, 2008 at 8:50 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > The releases have been made, so both the 3.0 branch and the trunk (2.6) are > now open for commits. Remember, there's only one more planned beta, and we > /really/ want to try to hit the October 1st deadline. Let's do everything > we can to stabilize these releases, address the blockers, and turn those > buildbots green. Thanks Barry! Indeed, I want everyone to focus on stabilization and release blockers (and the occasional speed-up). Be extra careful with what you submit between now and October, ask for a code review unless you're really sure. Also, remember, NO NEW FEATURES! > Thanks everyone. > - -Barry And thanks Barry for doing the release!!! -- --Guido van Rossum (home page: http://www.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] Implementing restricted Python in Zope2
> I would like to know how much the AST have been changed on moving from > python2.4 to python 2.5 so that I can bring the corresponding changes > in Zope2 to get it adapted to those changes in the AST. Notice that Parser/Python.asdl is new in Python 2.5, so (by today's terminology) Python 2.4 did not really have any AST. The relevant NEWS entry is - A new AST parser implementation was completed. The abstract syntax tree is available for read-only (non-compile) access to Python code; an _ast module was added. Python's prior notion of abstract syntax (which is rather a CST) directly reflects from the grammar; do svn log Grammar/Grammar to find out what exactly was changed. Regards, Martin ___ 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-3000] No beta2 tonight
On Thu, Jul 17, 2008 at 7:37 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake <[EMAIL PROTECTED]> wrote: >> On Jul 17, 2008, at 7:27 PM, Martin v. Löwis wrote: >>> >>> bsddb is in a very bad shape, as the 2.6 code hasn't been merged into >>> 3k. I somewhat doubt that this gets resolved before the release, so >>> bsddb users might need to skip 3.0. >> >> >> In fact, bsddb as packages in core Python has rarely been in good shape. >> >> Has anyone actually considered that bsddb might do better if maintained >> strictly as an external package? That would make it easier for the any >> maintainers to release updates, and removes a source of frustration for >> users who either don't need it or would rather wait for a happier version. >> >> I think this is worth considering. I vaguely recall that the bsddb module >> was maintained before it was incorporated into the core Python release. > > +1. In my recollection maintaining bsddb has been nothing but trouble > right from the start when we were all sitting together at "Zope Corp > North" in a rented office in McLean... We can remove it from 3.0. We > can't really remove it from 2.6, but we can certainly start > end-of-lifing it in 2.6. > Unless I hear otherwise, I will add it to PEP 3108. -Brett ___ 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] assertRaises
On Fri, Jul 18, 2008 at 8:51 AM, Mark Hammond <[EMAIL PROTECTED]> wrote: >> >> Let's just make assertRaises return the exception instance, it seems >> >> like it feels the need correctly. >> > >> > and I meant "fills", not "feels", obviously... >> >> +1 : enriching the existing method in a way that's perfectly >> transparent and innocuous to all existing uses _feels_ right, because >> it's more practical. > > For the record, and primarily to give the champion of this proposal a little > more resolve the run the python-dev gauntlet on this issue given the recent > - err - spirited discussions, I'm also strongly +1 on this idea. > I've got code and tests for this. I'll file a patch on the tracker as soon as I get the chance -- Internet is dicey at the moment. jml ___ 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] git repositories for trunk and py3k
On Tue, Jul 15, 2008 at 2:31 PM, Neil Schemenauer <[EMAIL PROTECTED]> wrote: > Benjamin Peterson <[EMAIL PROTECTED]> wrote: >> Can we push branches? > > The git-daemon is setup as read-only. If you have write access to > the SVN repository then you can push back changes using git-svn. > That's quite a nice way to work, IMHO and provides an easy path for > people who are used to Subversion and want to dip their toe in the > dvcs waters. > > While there is no support on code.python.org for publishing your own > git branches, there's no reason why you couldn't publish a branch > using some other host (it's a dvcs after all). In the short term, > perhaps using private branches in combination with "git > format-patch" and email is the easiest process. > So I have a change that I have in git. I would like to just push it to svn through git. I ran ``git svn dcommit``, but then a ton of stuff came streaming by on my terminal. Is that normal? Also, how does one refer to revisions for things like ``git diff``? Is it really the commit commit number (which I think is something like a SHA-1)? -Brett ___ 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] git repositories for trunk and py3k
[back on the list] On Thu, Jul 17, 2008 at 11:24:16PM -0700, Brett Cannon wrote: > Turned out to be a rebuild:: > > > r65077 = 82d954e8c20c91562c4c660859d17756cba10992 > r65082 = 1c75cce93c2ef2ec87e801888638cfdf5d2ff29a > r65085 = 3143c2fbe7315afd29496dc0cdac3122bed30536 > Done rebuilding .git/svn/git-svn/.rev_map.6015fed2-1504-0410-9fe1-9d1591cc4771 > > How do I know what is going to be sent? ``git log`` seems to suggest > something by not listing a git-svn-id for my last commit, but is that > really the best I got? The command git log git-svn.. will show you changes in your HEAD (by default "master") tree that are not in the remote tree (git-svn). > Is there some other way to see what will be pushed? I like running "gitk" before I push something. > And how do I diff easily between commits? It depends on what you want, exactly. Maybe you can describe some use cases. A DVCS can't use identify revisions like SVN does. Generally I find myself using heads or tags to identify versions in combination with the ^ operator. For example, git diff HEAD^ would show the difference between the current working tree and the commit before the head of the stored tree. If you want the patch for a single commit, use "git show ". For example, "git show" will display the last commit. To see amk's typo fix: git show 6cadb9c1b7e30a8b66cdba01cd79aa6397a07080 You can also abbreviate the commit id, eg. git show 6cadb9 As I say in my guide, "git format-patch" and "git am" are very handy when slinging patches around (e.g. to and from a bug tracker or mailing list). HTH, Neil ___ 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
