From python-dev Fri May 06 10:20:31 2005 From: Toby Dickenson Date: Fri, 06 May 2005 10:20:31 +0000 To: python-dev Subject: Re: [Python-Dev] PEP 340: Non-looping version (aka PEP 310 redux) Message-Id: <200505061120.31117.tdickenson () devmail ! geminidataloggers ! co ! uk> X-MARC-Message: https://marc.info/?l=python-dev&m=111537484230867 On Thursday 05 May 2005 16:03, Nick Coghlan wrote: > The discussion on the meaning of break when nesting a PEP 340 block > statement inside a for loop has given me some real reasons to prefer PEP > 310's single pass semantics for user defined statements That also solves a problem with resource acquisition block generators that I hadnt been able to articulate until now. What about resources whose lifetimes are more complex than a lexical block, where you cant use a block statement? It seems quite natural for code that want to manage its own resources to call __enter__ and __exit__ directly. Thats not true of the block generator API. -- Toby Dickenson _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-dev%40progressive-comp.com