Originally, this was to avoid running doctests over text files that were not to be run, to separate them. For example, sometimes a README.txt or another file can present a piece of code that would involved too much test fixture. But I agree that this is an exception, and docs/ alone (not doc/) would be fine.
David Bain wrote: > > Other conventions, I've seen, (I really mean archgenxml) seem to use a > doc/ folder for doctests. Why not stick to that? > > On Nov 29, 2007 6:39 AM, Tarek Ziadé <[EMAIL PROTECTED]> wrote: >> >> You can use it already in IngeniSkel package: >> >> $ easy_install IngeniSkel >> $ cd /to/my/package >> $ paster create -t iw_content MyATType >> >> But it relies on postconditions we use in our plone products >> (having a doctests folder, having a test folder, etc) >> >> I am going to backport it in Mustapha branch asap. >> >> Now this makes me wonder something about ZopeSkel and about >> how doctests are used in Plone. >> >> We have set here a standard: all doctests .txt files are grouped into a >> doctests >> subfolder in all our packages for three reasons: >> >> 1. it is less confusing for people to get and read them (in zope 3 they >> are >> all over the place it's a bit disturbing) >> 2. it helps us automate the documentation process >> 3. it provides a simple way to hook the doctests into the test campaing >> (==one file in tests/ to call all doctests in /doctests that ends with >> *.txt) (with the benefit of -m to run just one doctest) >> >> So my question is: what would you think guys about having a standard >> doctests folder created by >> ZopeSkel for all templates, so it would provide a standard way to run an >> get >> them ? >> and furthermore in Plone ? (i am sure there are work in progress in the >> area though..) >> >> >> Regards >> >> >> Tarek >> >> >> >> David Bain wrote: >> > >> > I stand ready to test it. >> > >> > On Nov 26, 2007 9:39 AM, Tarek Ziadé <[EMAIL PROTECTED]> wrote: >> >> >> >> Thanks Wichert and Martin, I am going to see with Mustapha >> >> >> >> >> >> >> >> Martin Aspeli wrote: >> >> > >> >> > Wichert Akkerman wrote: >> >> >> Previously Tarek Ziadé wrote: >> >> >>> Hi all, >> >> >>> >> >> >>> We have created a few templates on the top of ZopeSkel here to be >> >> able >> >> >>> to do >> >> >>> micro-templating in our Plone Products. The idea is to be able for >> >> >>> example >> >> >>> to inject a new archetype content type in an existing plone 3 >> >> product, >> >> >>> with >> >> >>> the paster. The missing feature was to be able to modify existing >> >> files >> >> >>> in >> >> >>> the product, such as the profile (types.xml, profiles.zcml, etc..) >> or >> >> in >> >> >>> the >> >> >>> interfaces. >> >> >>> >> >> >>> So what we have now is the ability to call the paster like this: >> >> >>> >> >> >>> $ paster create -t plone my.product >> >> >>> $ cd my.product >> >> >>> $ paster create -t archetype MyContent >> >> >>> $ paster create -t archetype MyOtherContent >> >> >> >> >> >> This should be done as local templates. Is that what you are doing? >> >> >> Someone made a ZopeSkel branch to work on that, but I forgot who it >> >> was. >> >> > >> >> > Mustapha Benali - http://www.mustap.com/mustapzone >> >> > >> >> > Martin >> >> > >> >> > -- >> >> > Author of `Professional Plone Development`, a book for developers >> who >> >> > want to work with Plone. See http://martinaspeli.net/plone-book >> >> > >> >> > >> >> > _______________________________________________ >> >> > Product-Developers mailing list >> >> > [email protected] >> >> > http://lists.plone.org/mailman/listinfo/product-developers >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/ZopeSkel-addon-proposal-tf4874897s20094.html#a13950867 >> >> Sent from the Product Developers mailing list archive at Nabble.com. >> >> >> >> >> >> _______________________________________________ >> >> >> >> Product-Developers mailing list >> >> [email protected] >> >> http://lists.plone.org/mailman/listinfo/product-developers >> >> >> > >> > _______________________________________________ >> > Product-Developers mailing list >> > [email protected] >> > http://lists.plone.org/mailman/listinfo/product-developers >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/ZopeSkel-addon-proposal-tf4874897s20094.html#a14023749 >> >> Sent from the Product Developers mailing list archive at Nabble.com. >> >> >> _______________________________________________ >> Product-Developers mailing list >> [email protected] >> http://lists.plone.org/mailman/listinfo/product-developers >> > > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers > > -- View this message in context: http://www.nabble.com/ZopeSkel-addon-proposal-tf4874897s20094.html#a14036587 Sent from the Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
