Re: Cleaning up the Pylons GitHub project
I made this to track some data about the repositories : http://janitor.herokuapp.com/ . I may help have a clearer view about which repositories are orphaned (the one with dead links in the description, or with very old last commit). It's quite slow (like timeout slow) when the cache is cold (lots of github api requests to do), so please bear with it. Please suggest anything that might make it more useful. I'll clean up the code and push it to github in the next few days. Mike, for the description on github, an edit button appears when you hover the description. -- Georges Dubus -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/BxlLYwywMCAJ. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: Question about virginia
On 1 mar, 23:00, Tres Seaver tsea...@palladion.com wrote: I'm afraid the example doesn't defend against relative '..' at all. That's what I would have thought, but http://localhost:6543/../ redirects to http://localhost:6543/ (sorry, typo in the previous message). I thought this had something to do with virginia, but it seems that the .. is interpreted earlier in the framework. I fact, it looks like it's the expected behaviour for an url ( just try : http://groups.google.com/group/pylons-devel/../../.. ) The pattern of registering views and adapters against interfaces, rather than directly against classes, goes back to our Zope-ish roots. I think some of those interfaces are actually left over from the time when Chris re-wrote 'repoze.kiss' to function as a BFG-based application: in 'repoze.kiss', there were real views registered for all the interfaces. Historical reasons ? That's what I thought. But, as it's used as an example application, wouldn't it be less confusing for newcomers to clean the application from the bits that aren't useful any more, in order to get a minimal working example ? If that's a good, idea, I volonteer. Georges -- You received this message because you are subscribed to the Google Groups pylons-devel group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Question about virginia
Hi there I was looking at the virginia sample application, and I have a few question : - What mechanism protects the application from viewing the /../ dir ? I know the open method from Filesystem check the path before opening a file, but that doesn't explain that when going to the url http://localhost:6543/../ , I am redirect to http://localhost:6543/../ . - Is there a reason so much interfaces are used ? IFilesystem is never referenced outside of Filesystem, and IStructuredText isn't even implemented. Thank for helping me understand that. Cheers, Georges -- You received this message because you are subscribed to the Google Groups pylons-devel group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
