New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

have_directory_for_build AssertionError when installing with --no-cache-dir (19.0.1) #6197

Closed
cjerdonek opened this Issue Jan 24, 2019 · 17 comments

Comments

Projects
None yet
9 participants
@cjerdonek
Copy link
Member

cjerdonek commented Jan 24, 2019

  • pip version: 19.0.1

With the 19.0.1 release, some people are still reporting an AssertionError when installing with --no-cache-dir similar to the one in #6158. This issue is for the 19.0.1-specific issue as it is narrower in scope.

Here are details for a couple reports: #6158 (comment) and #6158 (comment)

The traceback looks like this:

Exception:
Traceback (most recent call last):
  File "/mnt/jenkins/workspace/venv/local/lib/python2.7/site-packages/pip/_internal/cli/base_command.py", line 176, in main
    status = self.run(options, args)
  File "/mnt/jenkins/workspace/venv/local/lib/python2.7/site-packages/pip/_internal/commands/install.py", line 346, in run
    session=session, autobuilding=True
  File "/mnt/jenkins/workspace/venv/local/lib/python2.7/site-packages/pip/_internal/wheel.py", line 886, in build
    assert have_directory_for_build
AssertionError

Some work-arounds (feel free to add to the list):

  • Use pip version 18.1.
  • Pass --no-use-pep517 in your invocation.
  • See issue #6158 for some other possibilities.
@pradyunsg

This comment has been minimized.

Copy link
Member

pradyunsg commented Jan 25, 2019

ISTM this is only happening on Alpine Linux -- could someone confirm whether that is the case?

@vinayan3

This comment has been minimized.

Copy link

vinayan3 commented Jan 25, 2019

@pradyunsg I had problems as well. Please see my dup issue #6192

@dknepprath

This comment has been minimized.

Copy link

dknepprath commented Jan 25, 2019

Same but Python 3.7

Exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/pip/_internal/cli/base_command.py", line 176, in main
    status = self.run(options, args)
  File "/usr/local/lib/python3.7/site-packages/pip/_internal/commands/install.py", line 346, in run
    session=session, autobuilding=True
  File "/usr/local/lib/python3.7/site-packages/pip/_internal/wheel.py", line 886, in build
    assert have_directory_for_build
AssertionError

Reverting to pip 18.1 worked for me.

@hrw

This comment has been minimized.

Copy link

hrw commented Jan 25, 2019

ISTM this is only happening on Alpine Linux -- could someone confirm whether that is the case?

debian:stretch-backports official image:

INFO:kolla.common.utils.openstack-base:Traceback (most recent call last):
INFO:kolla.common.utils.openstack-base:  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/pip/_internal/cli/base_command.py", line 176, in main
INFO:kolla.common.utils.openstack-base:    status = self.run(options, args)
INFO:kolla.common.utils.openstack-base:  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/pip/_internal/commands/install.py", line 346, in run
INFO:kolla.common.utils.openstack-base:    session=session, autobuilding=True
INFO:kolla.common.utils.openstack-base:  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/pip/_internal/wheel.py", line 886, in build
INFO:kolla.common.utils.openstack-base:    assert have_directory_for_build
INFO:kolla.common.utils.openstack-base:AssertionError
@gaborbernat

This comment has been minimized.

Copy link

gaborbernat commented Jan 25, 2019

@pfmoore I ran into this myself, basically just passing --no-cache breaks pip when discovering and installing a PEP-517 package. We need either to fallback to disable PEP-517 build, or instead use the TMPDIR env var.

Hitting this from jython that does not support pip cache mechanism inside virtualenv.

@eliasbrange

This comment has been minimized.

Copy link

eliasbrange commented Jan 25, 2019

Easily reproducable in docker:

# Same for 3.5.6, 3.6.8, etc.
FROM python:3.7.2-alpine

RUN pip3 install -U pip

RUN pip3 install --no-cache-dir pendulum

kumy added a commit to geokrety/geokrety-api that referenced this issue Jan 26, 2019

kumy added a commit to geokrety/geokrety-api that referenced this issue Jan 26, 2019

kumy added a commit to geokrety/geokrety-api that referenced this issue Jan 26, 2019

kumy added a commit to geokrety/geokrety-api that referenced this issue Jan 26, 2019

@gaborbernat

This comment has been minimized.

Copy link

gaborbernat commented Jan 28, 2019

The error is very cryptic here, I think pip should check before invoking wheel if the folder exists and raise a better readable error what folder is missing. At the moment this fails with an assertion error leaving the user clueless what folder is missing, making it harder to track down (e.g. incorrectly set pip cache dir, HOME env var, etc). It also does not state for which package build it failed (important if the install pulls in a lot of dependencies first).

@cosmith

This comment has been minimized.

Copy link

cosmith commented Jan 28, 2019

Using --no-use-pep517 didn't work for me, downgrading to 18.1 did (using FROM python:3.6-alpine)

pcrespov added a commit to pcrespov/osparc-simcore that referenced this issue Jan 28, 2019

Fixed storage Dockerfile image build:
 - Added workaround for pypa/pip#6197
 - Froze python2 requirements (virtualenv py2.7 would fail to install numpy)

@pcrespov pcrespov referenced this issue Jan 28, 2019

Merged

Is539/master build fails #540

5 of 5 tasks complete
@pradyunsg

This comment has been minimized.

Copy link
Member

pradyunsg commented Jan 28, 2019

Using --no-use-pep517 didn't work for me, downgrading to 18.1 did (using FROM python:3.6-alpine)

Could you provide us a reproducing case for this issue?

@cjerdonek

This comment has been minimized.

Copy link
Member Author

cjerdonek commented Jan 28, 2019

FYI, for the provided Dockerfile example, it is failing for:
<Link https://files.pythonhosted.org/packages/5b/57/71fc910edcd937b72aa0ef51c8f5734fbd8c011fa1480fce881433847ec8/pendulum-2.0.4.tar.gz#sha256=cf535d36c063575d4752af36df928882b2e0e31541b4482c97d63752785f9fcb (from https://pypi.org/simple/pendulum/) (requires-python:>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*)>
This means, for example, that the link.is_artifact check returns True:

elif autobuilding and req.link and not req.link.is_artifact:
# VCS checkout. Build wheel just for this run.
buildset.append((req, True))
else:

If it were instead a VCS url, it looks like the assertion would succeed.

What is the purpose of the assertion, btw? Should the above case be working for a link like that?

@pradyunsg pradyunsg added this to the 19.0 milestone Jan 28, 2019

@cjerdonek

This comment has been minimized.

Copy link
Member Author

cjerdonek commented Jan 28, 2019

So I'm wondering if this logic might be incorrect / is the culprit:

if not _contains_egg_info(base):
# E.g. local directory. Build wheel just for this run.
ephem_cache = True

It seems like ephem_cache should also be set to True if that condition isn't true and no cache directory is available.

raymondEhlers added a commit to raymondEhlers/OVERWATCH that referenced this issue Jan 29, 2019

Work around bug in pip
Issue described here: pypa/pip#6197

pcrespov added a commit to ITISFoundation/osparc-simcore that referenced this issue Jan 29, 2019

Is539/master build fails (#540)
* minor cleanup

* Fixed storage Dockerfile image build:
 - Added workaround for pypa/pip#6197
 - Froze python2 requirements (virtualenv py2.7 would fail to install numpy)

* Fixes director Dockerfile using same workaround in pip as with storage

* Applies pip workaround to sidecar Dockerfile

* Applies pip workaround to webserver Dockerfile

* Applied pip workaround to backend dynamic services

* pip compiled py27.in -> py27.txt (pip-tools)
 Changes to be committed:
	new file:   services/storage/requirements/py27.in
	modified:   services/storage/requirements/py27.txt
@cjerdonek

This comment has been minimized.

Copy link
Member Author

cjerdonek commented Jan 29, 2019

FYI, I added a failing unit test for this issue here: #6219 (based on the Dockerfile example provided in this comment above)

Does anyone familiar with this part of the code know how the logic in compute_ephem_cache() should be changed to make the have_directory_for_build assertion succeed?

dcramer added a commit to getsentry/zeus that referenced this issue Jan 31, 2019

ricardbejarano added a commit to ricardbejarano/certbot that referenced this issue Feb 1, 2019

added temporary workaround to "assert have_directory_for_build" Asser…
…tionError, caused by github.com/pypa/pip/issues/6197; causes larger image

sladyn98 added a commit to sladyn98/conpot that referenced this issue Feb 2, 2019

docker/dockerfile:Updated dockerfile
With the recent update to pip 19.01 there was a build slight issue with the docker commands, refer here:
pypa/pip#6197

sladyn98 added a commit to sladyn98/conpot that referenced this issue Feb 2, 2019

docker/dockerfile:Updated dockerfile
With the recent update to pip 19.01 there was a build slight issue with the docker commands, refer here:
pypa/pip#6197

xandfury added a commit to mushorg/conpot that referenced this issue Feb 2, 2019

updated dockerfile (#429) - related (#428)
With the recent update to pip 19.01 there was a build slight issue with the docker commands, refer here:
pypa/pip#6197
@pradyunsg

This comment has been minimized.

Copy link
Member

pradyunsg commented Feb 2, 2019

@cjerdonek figured out a nice fix for this in #6219 and that's now merged. I'll make a 19.0.2 in the coming week, with that fix and more.

I'll go ahead and close this issue. I'll ping here when the release is made.

@pradyunsg pradyunsg closed this Feb 2, 2019

Yajo added a commit to Tecnativa/docker-duplicity that referenced this issue Feb 4, 2019

Workaround to pip bug
Recent builds failed to a pip bug.

Revert this commit once we use pip 19.0.2 (see pypa/pip#6197 (comment)).

@pganssle pganssle referenced this issue Feb 6, 2019

Open

Explicitly declare our build backend #1674

0 of 1 task complete

betatim added a commit to betatim/mybinder.org-deploy that referenced this issue Feb 8, 2019

Bring in repo2docker changes to work around pip bug
The latest version of pip (19.0.2) have a bug related to cache dirs
pypa/pip#6197
@pradyunsg

This comment has been minimized.

Copy link
Member

pradyunsg commented Feb 9, 2019

pip 19.0.2 has been released with a fix for this.

hoellen added a commit to hoellen/dockerfiles that referenced this issue Feb 9, 2019

maxandersen added a commit to home-assistant/home-assistant-cli that referenced this issue Feb 10, 2019

fix(docker): Avoid pip 19.0.1 bug
Why:

 * build was failing as described in pypa/pip#6197

This change addreses the need by:

 * force upgrade of pip as that makes it at least pass on my machine docker
   builds.

@pradyunsg pradyunsg unpinned this issue Feb 11, 2019

23doors added a commit to Syncano/syncano-platform that referenced this issue Feb 11, 2019

23doors added a commit to Syncano/syncano-platform that referenced this issue Feb 11, 2019

Differentiate between eu1 and us1 hosting cnames (#31)
* Differentiate between eu1 and us1 hosting cnames

* upgrade pip to circumvent pypa/pip#6197

* typo

* lint

@23doors 23doors referenced this issue Feb 11, 2019

Merged

Release #32

bors bot added a commit to mozilla/normandy that referenced this issue Feb 11, 2019

Merge #1726 #1732
1726: Update python:3.7-slim Docker digest to 8a125f6 r=peterbe a=renovate[bot]

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| python | digest | `3.7-slim` -> `8a125f6` |


1732: Scheduled weekly dependency update for week 06 r=peterbe a=pyup-bot






### Update [botocore](https://pypi.org/project/botocore) from **1.12.86** to **1.12.91**.


<details>
  <summary>Changelog</summary>
  
  
   ### 1.12.91
   ```
   =======

* api-change:``discovery``: Update discovery client to latest version
* api-change:``ecs``: Update ecs client to latest version
* api-change:``dlm``: Update dlm client to latest version
   ```
   
  
  
   ### 1.12.90
   ```
   =======

* api-change:``es``: Update es client to latest version
* api-change:``medialive``: Update medialive client to latest version
* api-change:``gamelift``: Update gamelift client to latest version
* api-change:``robomaker``: Update robomaker client to latest version
   ```
   
  
  
   ### 1.12.89
   ```
   =======

* api-change:``ec2``: Update ec2 client to latest version
* api-change:``fsx``: Update fsx client to latest version
   ```
   
  
  
   ### 1.12.88
   ```
   =======

* api-change:``shield``: Update shield client to latest version
* api-change:``servicecatalog``: Update servicecatalog client to latest version
* api-change:``ec2``: Update ec2 client to latest version
   ```
   
  
  
   ### 1.12.87
   ```
   =======

* api-change:``ecs``: Update ecs client to latest version
* api-change:``application-autoscaling``: Update application-autoscaling client to latest version
* api-change:``workspaces``: Update workspaces client to latest version
* api-change:``codecommit``: Update codecommit client to latest version
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/botocore
  - Changelog: https://pyup.io/changelogs/botocore/
  - Repo: https://github.com/boto/botocore
</details>





### Update [python-dateutil](https://pypi.org/project/python-dateutil) from **2.7.5** to **2.8.0**.


<details>
  <summary>Changelog</summary>
  
  
   ### 2.8.0
   ```
   ==========================

Data updates
------------

- Updated tzdata version to to 2018i.


Features
--------

- Added support for ``EXDATE`` parameters when parsing ``rrule`` strings.
  Reported by mlorant (gh issue 410), fixed by nicoe (gh pr 859).
- Added support for sub-minute time zone offsets in Python 3.6+.
  Fixed by cssherry (gh issue 582, pr 763)
- Switched the ``tzoffset``, ``tzstr`` and ``gettz`` caches over to using weak
  references, so that the cache expires when no other references to the
  original ``tzinfo`` objects exist. This cache-expiry behavior is not
  guaranteed in the public interface and may change in the future. To improve
  performance in the case where transient references to the same time zones
  are repeatedly created but no strong reference is continuously held, a
  smaller &quot;strong value&quot; cache was also added. Weak value cache implemented by
  cs-cordero (gh pr 672, 801), strong cache added by
  Gökçen Nurlu (gh issue 691, gh pr 761)


Bugfixes
--------

- Added time zone inference when initializing an ``rrule`` with a specified
  ``UNTIL`` but without an explicitly specified ``DTSTART``; the time zone
  of the generated ``DTSTART`` will now be taken from the ``UNTIL`` rule.
  Reported by href (gh issue 652). Fixed by absreim (gh pr 693).
- Fixed an issue where ``parser.parse`` would raise ``Decimal``-specific errors
  instead of a standard ``ValueError`` if certain malformed values were parsed
  (e.g. ``NaN`` or infinite values). Reported and fixed by
  amureki (gh issue 662, gh pr 679).
- Fixed issue in ``parser`` where a ``tzinfos`` call explicitly returning
  ``None`` would throw a ``ValueError``.
  Fixed by parsethis (gh issue 661, gh pr 681)
- Fixed incorrect parsing of certain dates earlier than 100 AD when repesented
  in the form &quot;%B.%Y.%d&quot;, e.g. &quot;December.0031.30&quot;. (gh issue 687, pr 700)
- Add support for ISO 8601 times with comma as the decimal separator in the
  ``dateutil.parser.isoparse`` function. (gh pr 721)
- Changed handling of ``T24:00`` to be compliant with the standard. ``T24:00``
  now represents midnight on the *following* day.
  Fixed by cheukting (gh issue 658, gh pr 751)
- Fixed an issue where ``isoparser.parse_isotime`` was unable to handle the
  ``24:00`` variant representation of midnight. (gh pr 773)
- Added support for more than 6 fractional digits in `isoparse`.
  Reported and fixed by jayschwa (gh issue 786, gh pr 787).
- Added &#39;z&#39; (lower case Z) as valid UTC time zone in isoparser.
  Reported by cjgibson (gh issue 820). Fixed by Cheukting (gh pr 822)
- Fixed a bug with base offset changes during DST in ``tzfile``, and refactored
  the way base offset changes are detected. Originally reported on
  StackOverflow by MartinThoma. (gh issue 812, gh pr 810)
- Fixed error condition in ``tz.gettz`` when a non-ASCII timezone is passed on
  Windows in Python 2.7. (gh issue 802, pr 861)
- Improved performance and inspection properties of ``tzname`` methods.
  (gh pr 811)
- Removed unnecessary binary_type compatibility shims.
  Added by jdufresne (gh pr 817)
- Changed ``python setup.py test`` to print an error to ``stderr`` and exit
  with 1 instead of 0. Reported and fixed by hroncok (gh pr 814)
- Added a ``pyproject.toml`` file with build requirements and an explicitly
  specified build backend. (gh issue 736, gh prs 746, 863)


Documentation changes
---------------------

- Added documentation for the ``rrule.rrulestr`` function.
  Fixed by prdickson (gh issue 623, gh pr 762)
- Added documentation for ``dateutil.tz.gettz``.
  Fixed by weatherpattern (gh issue 647, gh pr 704)
- Add documentation for the ``dateutil.tz.win`` module and mocked out certain
  Windows-specific modules so that autodoc can still be run on non-Windows
  systems. (gh issue 442, pr 715)
- Added changelog to documentation. (gh issue 692, gh pr 707)
- Changed order of keywords in the ``rrule`` docstring.
  Reported and fixed by rmahajan14 (gh issue 686, gh pr 695).
- Improved documentation on the use of ``until`` and ``count`` parameters in
  ``rrule``. Fixed by lucaferocino (gh pr 755).
- Added an example of how to use a custom ``parserinfo`` subclass to parse
  non-standard datetime formats in the examples documentation for ``parser``.
  Added by prdickson (gh 753)
- Added doctest examples to ``tzfile`` documentation.
  Patch by weatherpattern (gh pr 671)
- Updated the documentation for ``relativedelta``&#39;s ``weekday`` arguments.
  Fixed by kvn219 huangy22 and ElliotJH (gh pr 673)
- Improved explanation of the order that ``relativedelta`` components are
  applied in. Fixed by kvn219 huangy22 and ElliotJH (gh pr 673)
- Expanded the description and examples in the ``relativedelta`` class.
  Contributed by andrewcbennett (gh pr 759)
- Improved the contributing documentation to clarify where to put new changelog
  files. Contributed by andrewcbennett (gh pr 757)
- Fixed a broken doctest in the ``relativedelta`` module.
  Fixed by nherriot (gh pr 758).
- Changed the default theme to ``sphinx_rtd_theme``, and changed the sphinx
  configuration accordingly. (gh pr 707)
- Reorganized ``dateutil.tz`` documentation and fixed issue with the
  ``dateutil.tz`` docstring. (gh pr 714)
- Cleaned up malformed RST in the ``tz`` documentation.
  (gh issue 702, gh pr 706)
- Corrected link syntax and updated URL to https for ISO year week number
  notation in ``relativedelta`` examples. (gh issue 670, pr 711)


Misc
----

- GH 674, GH 688, GH 699, GH 720, GH 723, GH 726, GH 727, GH 740,
  GH 750, GH 760, GH 767, GH 772, GH 773, GH 780, GH 784, GH 785,
  GH 791, GH 799, GH 813, GH 836, GH 839, GH 857
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/python-dateutil
  - Changelog: https://pyup.io/changelogs/python-dateutil/
  - Docs: https://dateutil.readthedocs.io
</details>





### Update [s3transfer](https://pypi.org/project/s3transfer) from **0.1.13** to **0.2.0**.


<details>
  <summary>Changelog</summary>
  
  
   ### 0.2.0
   ```
   =====

* feature:``ProcessPoolDownloader``: Add ``ProcessPoolDownloader`` class to speed up download throughput by using processes instead of threads.
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/s3transfer
  - Changelog: https://pyup.io/changelogs/s3transfer/
  - Repo: https://github.com/boto/s3transfer
</details>





### Update [setuptools](https://pypi.org/project/setuptools) from **40.7.3** to **40.8.0**.


<details>
  <summary>Changelog</summary>
  
  
   ### 40.8.0
   ```
   -------

* 1652: Added the ``build_meta:__legacy__`` backend, a &quot;compatibility mode&quot; PEP 517 backend that can be used as the default when ``build-backend`` is left unspecified in ``pyproject.toml``.
* 1635: Resource paths are passed to ``pkg_resources.resource_string`` and similar no longer accept paths that traverse parents, that begin with a leading ``/``. Violations of this expectation raise DeprecationWarnings and will become errors. Additionally, any paths that are absolute on Windows are strictly disallowed and will raise ValueErrors.
* 1536: ``setuptools`` will now automatically include licenses if ``setup.cfg`` contains a ``license_file`` attribute, unless this file is manually excluded inside ``MANIFEST.in``.
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/setuptools
  - Changelog: https://pyup.io/changelogs/setuptools/
  - Repo: https://github.com/pypa/setuptools
</details>





### Update [boto3](https://pypi.org/project/boto3) from **1.9.86** to **1.9.91**.


<details>
  <summary>Changelog</summary>
  
  
   ### 1.9.91
   ```
   ======

* api-change:``discovery``: [``botocore``] Update discovery client to latest version
* api-change:``ecs``: [``botocore``] Update ecs client to latest version
* api-change:``dlm``: [``botocore``] Update dlm client to latest version
   ```
   
  
  
   ### 1.9.90
   ```
   ======

* api-change:``es``: [``botocore``] Update es client to latest version
* api-change:``medialive``: [``botocore``] Update medialive client to latest version
* api-change:``gamelift``: [``botocore``] Update gamelift client to latest version
* api-change:``robomaker``: [``botocore``] Update robomaker client to latest version
   ```
   
  
  
   ### 1.9.89
   ```
   ======

* api-change:``ec2``: [``botocore``] Update ec2 client to latest version
* api-change:``fsx``: [``botocore``] Update fsx client to latest version
   ```
   
  
  
   ### 1.9.88
   ```
   ======

* api-change:``shield``: [``botocore``] Update shield client to latest version
* api-change:``servicecatalog``: [``botocore``] Update servicecatalog client to latest version
* api-change:``ec2``: [``botocore``] Update ec2 client to latest version
   ```
   
  
  
   ### 1.9.87
   ```
   ======

* api-change:``ecs``: [``botocore``] Update ecs client to latest version
* api-change:``application-autoscaling``: [``botocore``] Update application-autoscaling client to latest version
* api-change:``workspaces``: [``botocore``] Update workspaces client to latest version
* api-change:``codecommit``: [``botocore``] Update codecommit client to latest version
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/boto3
  - Changelog: https://pyup.io/changelogs/boto3/
  - Repo: https://github.com/boto/boto3
</details>





### Update [Django](https://pypi.org/project/Django) from **2.0.10** to **2.0.12**.


<details>
  <summary>Changelog</summary>
  
  
   ### 2.0.12
   ```
   ===========================

*February 11, 2019*

Django 2.0.12 fixes a packaging error in 2.0.11.

Bugfixes
========

* Corrected packaging error from 2.0.11 (🎫`30175`).


===========================
   ```
   
  
  
   ### 2.0.11
   ```
   ===========================

*February 11, 2019*

Django 2.0.11 fixes a security issue in 2.0.10.

CVE-2019-6975: Memory exhaustion in ``django.utils.numberformat.format()``
--------------------------------------------------------------------------

If ``django.utils.numberformat.format()`` -- used by ``contrib.admin`` as well
as the the ``floatformat``, ``filesizeformat``, and ``intcomma`` templates
filters -- received a ``Decimal`` with a large number of digits or a large
exponent, it could lead to significant memory usage due to a call to
``&#39;{:f}&#39;.format()``.

To avoid this, decimals with more than 200 digits are now formatted using
scientific notation.


===========================
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/django
  - Changelog: https://pyup.io/changelogs/django/
  - Homepage: https://www.djangoproject.com/
</details>





### Update [pytest-testrail](https://pypi.org/project/pytest-testrail) from **2.3.2** to **2.3.3**.


<details>
  <summary>Changelog</summary>
  
  
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/pytest-testrail
  - Changelog: https://pyup.io/changelogs/pytest-testrail/
  - Repo: http://github.com/allankp/pytest-testrail/
</details>





### Update [pip](https://pypi.org/project/pip) from **19.0.1** to **19.0.2**.


<details>
  <summary>Changelog</summary>
  
  
   ### 19.0.2
   ```
   ===================

Bug Fixes
---------

- Fix a crash where PEP 517-based builds using ``--no-cache-dir`` would fail in
  some circumstances with an ``AssertionError`` due to not finalizing a build
  directory internally. (`6197 &lt;https://github.com/pypa/pip/issues/6197&gt;`_)
- Provide a better error message if attempting an editable install of a
  directory with a ``pyproject.toml`` but no ``setup.py``. (`6170 &lt;https://github.com/pypa/pip/issues/6170&gt;`_)
- The implicit default backend used for projects that provide a ``pyproject.toml``
  file without explicitly specifying ``build-backend`` now behaves more like direct
  execution of ``setup.py``, and hence should restore compatibility with projects
  that were unable to be installed with ``pip`` 19.0. This raised the minimum
  required version of ``setuptools`` for such builds to 40.8.0. (`6163 &lt;https://github.com/pypa/pip/issues/6163&gt;`_)
- Allow ``RECORD`` lines with more than three elements, and display a warning. (`6165 &lt;https://github.com/pypa/pip/issues/6165&gt;`_)
- ``AdjacentTempDirectory`` fails on unwritable directory instead of locking up the uninstall command. (`6169 &lt;https://github.com/pypa/pip/issues/6169&gt;`_)
- Make failed uninstalls roll back more reliably and better at avoiding naming conflicts. (`6194 &lt;https://github.com/pypa/pip/issues/6194&gt;`_)
- Ensure the correct wheel file is copied when building PEP 517 distribution is built. (`6196 &lt;https://github.com/pypa/pip/issues/6196&gt;`_)
- The Python 2 end of life warning now only shows on CPython, which is the
  implementation that has announced end of life plans. (`6207 &lt;https://github.com/pypa/pip/issues/6207&gt;`_)

Improved Documentation
----------------------

- Re-write README and documentation index (`5815 &lt;https://github.com/pypa/pip/issues/5815&gt;`_)
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/pip
  - Changelog: https://pyup.io/changelogs/pip/
  - Homepage: https://pip.pypa.io/
</details>







Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: pyup-bot <github-bot@pyup.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment