Closed ric03uec closed 10 years ago
This looks like it errored before even getting to any Python Project Template-related code. A few questions:
paver test_all
run correctly?Sorry for not being very clear earlier.
I went through all the steps and paver test_all
run correctly with all builds passing,
the tox
command produced the error i provided, the following lines were output before the one I had earlier mentioned.
I'm trying to run automated builds using the travis.yml file but tox
command is failing.
Successfully installed tox virtualenv py
Cleaning up...
Executing python internal/generate.py
Completed python internal/generate.py with output
Substituting ./setup.py.tpl -> ./setup.py
Substituting ./pavement.py.tpl -> ./pavement.py
Substituting ./LICENSE.tpl -> ./LICENSE
Substituting ./tests/test_main.py.tpl -> ./tests/test_main.py
Substituting ./docs/Makefile.tpl -> ./docs/Makefile
Substituting ./docs/make.bat.tpl -> ./docs/make.bat
Substituting ./docs/source/index.rst.tpl -> ./docs/source/index.rst
Substituting ./docs/source/conf.py.tpl -> ./docs/source/conf.py
Substituting ./docs/source/README.tpl -> ./docs/source/README
Substituting ./my_module/__init__.py.tpl -> ./my_module/__init__.py
Substituting ./my_module/main.py.tpl -> ./my_module/main.py
Renaming the package: my_module -> my_module
Making main script executable...
Removing internal Travis-CI test file...
Revising `LICENSE' file...
Removing internal directory...
To finish project setup:
1. Change the `classifiers' keyword in `setup.py' as necessary.
2. Change the license in `setup.py' and replace the generated `LICENSE' file
with the one of your choice. If you would like to use the MIT license, no
change is necessary.
3. Install `argparse' package when developing on Python 2.6.
4. Change `README.rst' to your own text.
Executing tox
GLOB sdist-make: /home/someuser/virtualenvs/python/2.7/projects/pytemplate/workspace/setup.py
py27 create: /home/someuser/virtualenvs/python/2.7/pytemplate/workspace/.tox/py27
py27 installdeps: --no-deps, --requirement, /home/someuser/virtualenvs/python/2.7/projects/pytemplate/workspace/requirements-dev.txt
I still don't completely understand the problem, but I can guess based on the output. A couple more questions:
.travis.yml
from Python Project Template (PPT) in your generated project? If so, that's not what is intended and it won't work. The .travis.yml
in PPT is strictly for testing PPT only.More specifically, each clone of PPT that you are using for a project should "destroy itself" to become your project. That's why the internal files (the .travis.yml
file and the internal/
directory) are removed at generation. The generation script should only be run once -- manually, by you. Automated runs of the generation script are for testing PPT itself.
Let me know and we'll hopefully get it resolved :)
Got it fixed. Thanks for help. I was trying to run it on shippable.com which is a build platform(much like travis). The issue seemed to be somewhere in directory structure with too deep nesting resulting in unexpected errors and builds failing without giving any information. We changed the implementation and its working fine now.
OK, great! Let me know how PPT works out for you.
I cloned the repo and trying to run the tests for which i'm getting the following error. can you please help me out here.
Here i'm trying to run it from a virtualenv
I also tried to install tox and run the tests but same error is occurring again.