|
Size: 586
Comment:
|
Size: 747
Comment: turn links to non-existent pages links to things that exist
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| * build--["zc.buildout"]; (deployment solutions or ["Distribution Utilities"]) * test--["static source analysis"]; ["pytest"]; ["doctest"]; ["zope.testing"]; (testing taxonomy) |
* build--[http://www.python.org/pypi/zc.buildout zc.buildout]; (deployment solutions or DistributionUtilities) * test--["static source analysis"]; [http://docs.python.org/lib/module-unittest.html pytest]; [http://docs.python.org/lib/module-doctest.html doctest]; [http://www.python.org/pypi/zope.testing zope.testing]; (testing taxonomy) |
While there's a specific advocacy opportunity that inspires formation of this page in May 2007, the question legitimately recurs, and is likely to interest many readers.
"Application lifecycle" here encompasses such aspects of development as
- requirements--["UML"]
- design--
development--DevelopmentTools include IntegratedDevelopmentEnvironments and PythonEditors; ["implementation"]s; ...
build--[http://www.python.org/pypi/zc.buildout zc.buildout]; (deployment solutions or DistributionUtilities)
test--["static source analysis"]; [http://docs.python.org/lib/module-unittest.html pytest]; [http://docs.python.org/lib/module-doctest.html doctest]; [http://www.python.org/pypi/zope.testing zope.testing]; (testing taxonomy)