-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello,
here are some recent findings, that other plugin authors/maintainers may find helpful as well: I noticed that component names in the 'enable' attribute to trac.test.EnvironmentStub are required with correct casing for 0.11.x, while they're accepted regardless of character casing from Trac 0.12 onwards. I've found that the line packages = find_packages(exclude=['*.tests']) in Trac's setup.py prevents all the functional test methods from becoming packaged and installed. So no wonder, that any import from trac.tests or below must fail. Question: Does the above mean, that we have to include the functional tester stuff in each Trac plugin separately? At least I can't see another straight way. Sincerely, Steffen Hoffmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDeXbMACgkQ31DJeiZFuHfzzQCfejeJQ/7zfNI+GI5ZAlAgWMcl /GcAoL9oYfkaRIKgO9Ude2RclHNdfr8K =MEP6 -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
