[BangPypers] Testing Email with PDF Attachment

Hi Testing Email attachment after modifying the content filters option. Please bear with me if you get a chance to see this and wonky config. -- *Thanks & Regardskracekumar"Talk is cheap, show me the code" -- Linus Torvaldshttp://kracekumar.com *

[BangPypers] Testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Testing mailing list settings - Ignore. - -- - -- Software Architect/Consultant Cell: +919880078014 anandpil...@letterboxes.org Please note my updated email address

Re: [BangPypers] Testing for documentation as a release criterion

Nice to now you felt good on this suggestion..it just occurred sort of :)my experience with YAML says that, its best to use: load from syck and dump from yaml. if you are not going to dump YAML, and not going to work on complex YAML stuff...use syck for loadingyou'll be much happier with that.

Re: [BangPypers] Testing for documentation as a release criterion

On Thu, Jun 18, 2009 at 8:17 PM, Vishal wrote: > If you run PyLint on any Python file...it gives you documentation > percentage of functions, methods, class, modules in your code tree. > it prints that out as a table. if you can scrap that info from the > resulting file...that should help as well

Re: [BangPypers] Testing for documentation as a release criterion

If you run PyLint on any Python file...it gives you documentation percentage of functions, methods, class, modules in your code tree. it prints that out as a table. if you can scrap that info from the resulting file...that should help as well... basically it should be 100% for all the above..if not

Re: [BangPypers] Testing for documentation as a release criterion

I'm doing something similar for a nascent project at my workplace. My plan was to enforce some kind of structure as well. I'm not familar enough with Restructured Text and any of the other Python text processing libraries so I'm not sure what to do yet. You could perhaps also mandate an example for

[BangPypers] Testing for documentation as a release criterion

Hello, I am currently thinking about enforcing the following standard for a small demo project that might evolve into something larger pending approval(which was why the request for training programmes). Every module, every class and every function should have documentation. To enforce this, I wr