But, as a first guess, it seems
that people do find good uses for being able to return a value from a
block.
Probably 'continue ', which I had proposed earlier, is
awful syntax for returning a value from a block. But 'produce
' or s
struction, and people seemed to
like it. Take a look:
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/410692
--
Brian Beck
Adventurer of the First Order
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/p
mple requires two
fairly advanced techniques (inner functions, variables-as-arrays trick)
that would probably be lost on some python users (and make life more
difficult for the rest).
But I do see the appeal to having a non-looping 'with'. In many (most?)
uses of generators, '
ontinuations would help, but I'm not about to go
there :-).
If it is accepted that the thunk won't be callable at a later time, then I
think it would seem normal that a return statement would return from the
surrounding function.
-Brian
___
P
, to avoid exception weirdness,
f_exc_XXX.
In this way, calling the thunk is much like resuming a generator.
-Brian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.o
aims
every lock listed in the 'locks' key before starting.
The one big problem with this approach is that the build looks like it's
stalled while it waits for the lock: you get a big yellow box between the
time it is supposed to start and the t
>> seq = [1,2,3,4,5]
>> if any(seq, lambda x: x==5):
>> ...
>>
>> which is clearly more readable than
>>
>> reduce(seq, lambda x,y: x or y==5, False)
>
> How about this?
>
> if any(x==5 for x in seq):
Aren't all of th
Nick Coghlan wrote:
> Here's a fairly minimal proposal, which is closer to the existing 2.4
> structure:
>
> New Hierarchy
> ...
I also like this version.
--
Brian Beck
Adventurer of the First Order
___
Python-Dev mailing list
P
ve builds of both branches on the same page, which could be a
bit confusing (if the top line is red, does that mean the trunk is broken, or
the 2.4 branch?). Fixing this (by creating separate pages for each branch) is
high on the TODO list.
If there's any way I can help out furt
show specific ones (perhaps one primary builder for each
architecture). If the reverse-proxy or some sort of Apache URL-rewriting
allows you to add query parameters to the target URLs, you might be able to
hide these filtered views behind simple-looking status U
hat. It should be in the next release.
-Brian (running busy today, hoping to respond to the rest tonight)
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/op
the top-level
server.Site and the primary html.StatusResource object. But, as I said, my
twisted-web-foo is not strong, so I could be completely wrong about this.
cheers,
-Brian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.
exible enough to handle it.
> The current problem with this is that I don't know if the build step
> objects have access to a local data store -- so it could, say, count how
> many builds have been done to know to clobber every tenth one. The
> current code just chooses to clobber
grade or change the code on that side. The VC checkout/update operations
are an exception, since they may do several operations in a row (which would
mean a lot more latency to do them without support from code on the slave
side), and because I'm lazy and prefer to implemen
tatus event
delivery APIs in the buildbot which could cause a method to be called each
time a Step was started or finished, and these could just write new HTML to a
file. It would consume a bit more disk space, but would allow an external
webserver to provide truly read-only access to build status.
s supposed to.
cheers,
-Brian
___
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/archive%40mail-archive.com
f not, I'll write one before I
get the next release out.
thanks,
-Brian
___
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/archive%40mail-archive.com
Mercurial, I hoped
that any developers who've used a DVCS (and who are over 18 years
old) might like to participate in our survey and share your
experiences. (We followed your extensive discussions on the switch
with great interest.) Details on partcipating are below. Thanks
for yo
On 28-May-09, at 9:35 PM, Senthil Kumaran wrote:
On Wed, May 27, 2009 at 06:02:57PM -0600, Brian de Alwis wrote:
With Python having recently chosen to switch to Mercurial, I hoped
that any developers who've used a DVCS (and who are over 18 years
old) might like to participate in our s
for his source code and try to use type-defing as a bug-finder.
With thanks,
Brian
___
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
veloper) can then perform an
import as follows:
from miniframework import Application
instead of:
from miniframework.app import Application
This allows the public api be be cleaner, while still being efficient
by not loading all modules in __init__.py until the v
501 - 521 of 521 matches
Mail list logo
