pytest-sugar | default look and feel of py.test ( e.g | Plugin library

I am trying to install mysqlclient in virtrualenv on OSX high sierra, with python 3. And got the following error:

I am running a Cookiecutter django project in a docker environment and I would like to add new packages via pip. Specifically I want to add: djangorestframework-jwt

When I do: docker-compose -f local.yml run --rm django pip install it seems like it would be perfectly working because I get: Successfully installed PyJWT-1.7.1 djangorestframework-jwt-1.11.0

Now the problem is that it doesn't install it. It doesn't appear when I run pip freeze, and also not in pip list

Then I tried to put it into my requirements.txt file and run it with: docker-compose -f local.yml run --rm django pip install -r requirements/base.txt

Same result. It says that it is successfully installed but it is not. I thought it might be a problem with my django version and the package, but the same happens when I try to update my pip. It says it updated, but when I run pip install -upgrade pip I get again: You should consider upgrading via the 'pip install --upgrade pip' command.

I'm running out of options.

My requirements:

I'm using tox for my testing. Currently my tox.ini defines several commands:

In conftest.py I am loading the module blueprint.Manifest, which in turn loads the module Head for example. Please see minimal example at the bottom of the description. But I get the following error:

I am at the moment facing a weird behaviour when running Python doctests in Pytest (py.test). The following snippet highlights the bevaviour.

• The doctests do pass when the script is invoked via python2.7 ./weirdpytestbehaviour_test.py.
• The doctests do not pass when the script is invoked via py.test ./weirdpytestbehaviour_test.py --doctest-modules --tb=short.
• If I change the statement except CalledProcessError as e: into except Exception as e: the doctests then also pass with py.test.

It seems as py.test has some special treatment for the CalledProcessError exception type. It is very unintuitive that the code takes a different evaluation path when executed in py.test. How can I control or tweak that behaviour?

I am a complete beginner, but I have created a small website using Python / Django with the help of django-cookiecutter, including the deploy to Heroku instructions. I am in the process of deploying it for the first time to Heroku, however, the build is failing at the point in which it is running setup.py install for django-appconf, suggesting that it is due to the fact that Heroku already has the "Six" package.

The error message I am receiving is as follows:

I want to integrate my project into Travis-CI. My project involved a Flask web-server in Python with a postgresql database. All my tests use a web server running in debug mode. I'm trying to get this set up properly on Travis-CI and am having some troubles.

I'm building and testing under python 2.7 and 3.4, and the problem is my web server does not appear to start during the 3.4 build. The build for 2.7 starts first, runs fine, and all my tests pass, however the web server fails to start in the 3.4 build. When I run each build individually, both the 2.7 and 3.4 builds work fine and all tests pass. Is there a conflict between the web servers for each build? Here is my travis.yml file.