| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
The proper way to run setup.py is with "python setup.py". That allows
you to choose the right Python version to use.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This was done with the aid of the pep8 script, available by running
`easy_install pep8`.
It may be worth making this part of ./check, but that will require
putting pep8 into the development tools stratum.
This should be easy, given pep8 has no external dependencies.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
Plugins weren't installed because package installation doesn't by
default include subdirectories.
This would break system building on any morph which uses the plugins
instead of having system build built-in.
package_data seems to be the correct way to do this, as plugins aren't
library files since they have different loading characteristics, such
as different search paths and every found plugin is loaded, rather than
on-demand.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
We don't do releases, so having the version number in the source is
misleading. If and when we start doing numbered releases, it's easy
to add back. However, YAGNI and all that.
|
| | |
|
| |
|
