Re: svn pre-commit hook a bit dumb?

File a ticket. I agree, it should only look in .py files, so it doesn't get
tripped up on documentation etc.

-- 
Alexander Limi · http://limi.net


On Fri, Nov 27, 2009 at 1:16 AM, Raphael Ritz
<[email protected]>wrote:

> [not sure this is the right list for this but anyway ...]
>
> Hi,
>
> just tried to import an old package from a local repository to
> the collective as people wanted access to its code base but the
> import failed due to the check for "import pdb;pdb.set_trace()"
> in the pre-commit hook.
>
> Now, while I understand the intention here the offending statement
> in my case is *not* in code but in documentation in a restructured
> text file.
>
> Maybe to pre-commit hook could be made a bit more clever in
> restricting this check to Python source files (*.py) ?
>
> Should I file a ticket for this?
>
> Raphael
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Plone-website mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-website
> The Wiki: http://plone.org/development/current/projects/WebsiteTeam
>

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev

_______________________________________________
Plone-website mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-website
The Wiki: http://plone.org/development/current/projects/WebsiteTeam