Use a process compatible with the RTD build process.

This will allow them to share dependencies and avoid installing PyYAML twice.

Right now it puts in 2013/10/09...

Looks like this was intentional, but the Coveralls badge is still up on the README.

It might be helpful to provide a place holder for the template functionality so it can be grown with added features.

pep8, pylint, etc. are obviously not going to be confused with actual files/directories. Perhaps .PHONY should only be used when necessary (thus keeping the Makefile cleaner)?

My past two flights, I've tried to work on code. But inevitably, I'll touch something in the Makefile and it will try to install things without Internet. It would be cool if this could be handled gracefully.

Some options:

• check for Internet before installing
• let installs fail and warn about it
• add a variable to disable installs (e.g. NO_INTERNET=1 make do-stuff)

I've not seen a case where they would be helpful.

1. copy this package to /tmp
2. rename this package to match the outdated package
3. make clean-all in both
4. open a diff tool

Call pep8, pylint, etc. with the tests directory.

If there is a failure, the coverage report is unnecessary and forces extra scrolling.

Currently, the template suggests putting the tests in the package, but I'd like to remember the main arguments.

The first I can think of is that if you have doctests you can simply run your entire package through your test runner.

Travis can already do this with build matrices, but for every other CI service (like Wercker) it may be nice to have this capability.

Potentially the make dist dry run, could be replaced with an actual upload to https://testpypi.python.org/pypi.

This question (that I asked) continues to get more views, but the accepted answer is not the approach taken by this template.

This should test everything that #62 mentions.

Similar to:

# Test runner settings
...
UNIT_TEST_COVERAGE := 86
INTEGRATION_TEST_COVERAGE := 100

Either 100 or 0 can be the default.

See the bug experienced here: doorstop-dev/demo#7 (comment)

Now that RC1 is out (with RC2 coming in a few days) and py.test assert rewriting is fixed (pytest-dev/pytest#744) 3.5 should be added to the build matrix

https://speakerdeck.com/tylerdave/pyohio-2015-python-packaging-from-init-to-deploy

when not building on windows, the SYS_PYTHON variable is set as follows:

SYS_PYTHON := python$(PYTHON_MAJOR)

it should be something like:

SYS_PYTHON := python$(PYTHON_MAJOR).$(PYTHON_MINOR)

I've just started a new project and thought about using template-python. Unfortunately, I'll have to use Cython to speed up parts of my code. In the context of this framework, how do I proceed best in including Cython code?

I've found some resources on the web, which document my confusion perfectly:
http://pages.uoregon.edu/cfulton/posts/building_python_modules.html
http://comments.gmane.org/gmane.comp.python.cython.user/11186

Basically, I looks like the makefile could take over the generation of the .c files from the .pyx files and only the .c files are then mentioned as ext_modules in setuptools.setup.

Do you have any opinions or recommendations on this matter?

Some services look for this file when building an app.

Coveralls supports setting a minimum coverage percentage. If the threshold is not met, it will post a failing status to the GitHub Status API for that pull request. Using this instead of the current setup would let the coverage check fail the pull request checks separately from unit tests run by travis.

It seems like the dependencies installed by $ make depends-ci and $make depends-dev could be installed and used from the system Python to save time/space. In the Makefile, they could each be invoked by $(SYS_PYTHON) -m <name.

And submit to https://github.com/audreyr/cookiecutter?

If 3.4 is placed in .pydevproject, PyDev will default to 2.7. A fix needs to map all Python 3.x versions to 3.0 while keeping 2.x unchanged.

GitHub will link to this file: https://github.com/ionelmc/nose-htmloutput/issues/new

Or call this $ make setup.

Also, MIT is probably a better default license.

The --download-cache argument is now deprecated on pip: https://pip.pypa.io/en/latest/reference/pip_install.html#caching

I think we can simply remove the caching features provided by this template.

The supported Python versions should also be templated.

http://jinja.pocoo.org/docs/dev/templates/#equalto

I have created a number of projects from this python template and I would like them to benefit from the recent improvements to this template... is there an easy way to update the project structure for one of those projects from this newer template?

• Update .pylintrc: msg-template={msg_id} ({symbol}):{line:3d},{column}: {msg}
• Disable warnings by symbol name

IDEs sometimes have this feature, but Watchman could add this for everyone using a text editor and CLI.

• create a variable to control the HTML directory
• delete the directory when coverage results are cleared
• generate HTML reports before displaying text reports

pep257 moved: https://github.com/PyCQA/pydocstyle

And fail fast on long tests.

This will ensure novice users don't see weird issues trying to install Python 3 with Python 2's pip.