[NEW PORT] www/py3-requests: HTTP library written in Python for human beings

[cpm]

Summary

Python3 specific version for www/py-requests

[feld]

why is this port called py3-requests? the prefix for python ports should just be py-. The package will automatically be named to py31, 32, 33, 34, etc. I understand that this only supports python 3.x, but we still name the ports py-* unless there has been a policy change I'm unaware of.

[cpm]

In D6938#145519, @feld wrote:

why is this port called py3-requests? the prefix for python ports should just be py-. The package will automatically be named to py31, 32, 33, 34, etc. I understand that this only supports python 3.x, but we still name the ports py-* unless there has been a policy change I'm unaware of.

What do you suggest to do in this case?

Add www/py-request to RUN_DEPENDS and discard www/py3-requests
or
Commit www/py3-requests as a new port (we actually have some py3- ports into the ports tree, like py3-chardet port)

[feld]

I need to consult with someone who has more knowledge of python ports. I'm going to consult the handbook and see if anything is in there... also Mk/Uses/python.mk ... then maybe a portmgr. Sorry, just want this to be correct.

[cpm]

In D6938#145576, @feld wrote:

I need to consult with someone who has more knowledge of python ports. I'm going to consult the handbook and see if anything is in there... also Mk/Uses/python.mk ... then maybe a portmgr. Sorry, just want this to be correct.

OK, I agree with you.

At least, they aren't duplicate and the packages builders will work:
% make -C www/py-requests -VPKGNAME
py27-requests-2.10.0
% make -C www/py3-requests -VPKGNAME
py34-requests-2.10.0

[feld]

Python ports MUST be named py-<name> by default, unless there is a compelling case not to do so.

https://wiki.freebsd.org/Python/PortsPolicy

so let's keep it py-* not py3-*

[cpm]

Per Python Ports Policy: Discard www/py3-requests

[cpm]

We need this port to avoid failures from pkg-fallout.

[junovitch]

We don't want to duplicate the existing py-requests port when we do this. Take a look at https://svnweb.FreeBSD.org/ports/head/graphics/py3-pillow/ and note that port just uses this along with a few additional statements to set the correct things that are different from the master port. Please adjust this submission to mirror this.

MASTERDIR=      ${.CURDIR}/../py-pillow

I suspect when VARIANTS happens the py3-* ports will go away but a python@ person would be useful to ask on that for the long term plans.

[junovitch]

In D6938#145519, @feld wrote:

why is this port called py3-requests?

End users can do DEFAULT_VERSIONS and get all Python 3 ports but without VARIANTS the only way a pkg only user can get the Python 3 ports is with the py3-* versions.

[cpm]

In D6938#146097, @junovitch wrote:

We don't want to duplicate the existing py-requests port when we do this. Take a look at https://svnweb.FreeBSD.org/ports/head/graphics/py3-pillow/ and note that port just uses this along with a few additional statements to set the correct things that are different from the master port. Please adjust this submission to mirror this.

MASTERDIR=      ${.CURDIR}/../py-pillow

I suspect when VARIANTS happens the py3-* ports will go away but a python@ person would be useful to ask on that for the long term plans.

Ok, I'm working on it. Let me update the patch.

[cpm]

This py3-* port isn't necessary since py-socli has added python2 support.