On Tue, Jun 16, 2009 at 10:50:41AM -0700, Christopher Lee wrote: -> Hi Kenny, -> it is very helpful for us to see these kinds of problems. At a -> minimum it's information we should add to the documentation...
Hi Chris, I'm not entirely sure I agree about adding this kind of information to the docs. Perhaps I'm missing something, but this seems more like a programming error than a pygr error! Modifying the object you're looping over is never safe in Python unless it explicitly says it is, and since pygr is wrapping other Python objects, the behavior depends on the behavior of the wrapped objects. While this may be confusing, I don't think a specific warning is needed unless there's more to this than I realize. I do feel strongly about keeping the docs as lean as possible, containing primarily the absolutely critical information that you need to know in order to use a particular API, and then some linear tutorials that go into more depth and explain technical details and choices that need to be made. cheers, --titus -- C. Titus Brown, c...@msu.edu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
