Python package testing framework
It would be good to have some kind of CI framework for testing Python packages, specifically centered around transitions in major versions within the 2 and 3 families, as well as compatibility with Python 3 (perhaps via 2to3). Part of the idea includes promoting best practices for upstream authors so that consistency is encouraged (e.g. 'python setup.py test' works).
* build
* run upstream unit test
* 2to3
* report on ftbfs and test failures
* against any/every python version
Blueprint information
- Status:
- Not started
- Approver:
- Robbie Williamson
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Barry Warsaw
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Deferred
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
[qense 2010-05-08]
Would this also be something that could be used for a potential 'Ubuntu App Store' as some kind of automatic checker?
[barry 2010-05-24]
Possibly, but the App Store is way more than just Python applications. I'm trying to start with something more modest :)
Work items:
[barry] Specify test API with help from distutils-sig: TODO
[barry] Write guidelines for Hitchhikers Guide to Packaging docs: TODO
[barry] Quickly template for Python package best practices: INPROGRESS
[barry] investigate pypi:pyron for ideas/useful code: TODO
[barry] investigate paste for ideas/useful code: TODO
[barry] Spec out build system w/integration of isolated VMs: TODO
[barry] Build prototype CI w/Hudson and test with Cheeseshop packages using Python 2.6: TODO
[barry] Extend to use Python 2.7: TODO
[barry] Extend to run 2to3 and test with Python 3.1: TODO
[barry] Extend to use Python 3.2: TODO
[barry] Investigate automated or guided Trove classification setting: TODO
http://
http://
