On 7 March 2013 14:43, Steve Schmechel <[email protected]> wrote: > This still seems to come down to "fuzzy" requirement definitions. > What is your distinction between "users" and "developers"? > What functionality do you expect to control vs. other developers/users > controlling? > There is a range of answers for both questions that are workable, but you > seem to be talking about several points on each one at the same time. >
I'm unhappy that there is a case where pyramid will swallow developer errors. They happen. Even with test driven development. I think everything else about my use case is not of much relevance. However, my potential users are also developers. They currently write crappy code in python scripts, and I want them to put that code somewhere which suddenly it's available online. So I care about their experience, especially the edge cases which will hide their mistakes and give them incorrect results! Whining aside, I think there exists at least one good solution for my (admittedly unusual) case, and I'm greatful for the input from this thread. That said, I'm still sad that the edge case exists for all other pyramid users. Sure, it's just one edge case and there are more where that come from, but it's the sort of thing which can burn hours of time and confuse newbies into not trusting their eyes. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
