On 6/5/20 11:37 AM, Vladimir Sementsov-Ogievskiy wrote:
> 03.06.2020 03:15, John Snow wrote:
>> pipenv is a tool used for managing virtual environments with precisely
>> specified dependencies. It is separate from the dependencies listed in
>> setup.py, which are (by 'best practices') not supposed to be pinned.
>>
>> Note that pipenv is not required to install or use this module; this is
>> just a convenience for in-tree developing.
>>
>> Here, a "blank" pipfile is added with no dependencies, but specifies
>> Python 3.6 for the virtual environment.
>>
>> Pipfile will specify our version minimums, while Pipfile.lock specifies
>> an exact loudout of packages that were known to operate correctly. This
>> latter file provides the real value for easy setup of container images
>> and CI environments.
>>
>> Signed-off-by: John Snow <[email protected]>
>> ---
>> python/Pipfile | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>> create mode 100644 python/Pipfile
>>
>> diff --git a/python/Pipfile b/python/Pipfile
>> new file mode 100644
>> index 00000000000..9534830b5eb
>> --- /dev/null
>> +++ b/python/Pipfile
>> @@ -0,0 +1,11 @@
>> +[[source]]
>> +name = "pypi"
>> +url = "https://pypi.org/simple";
>> +verify_ssl = true
>
> I didn't find what does [[source]] mean, but seems it a standard header
> of Pipfile.
>
> Not sure, how much sense in it, but:
> Reviewed-by: Vladimir Sementsov-Ogievskiy <[email protected]>
>
Yeah, this is generated by the pipenv tool. I assume this describes
which repositories should be probed for downloading packages.
--js
