On 18/01/15 09:34, W. Martin Borgert wrote:
> On 2015-01-18 07:39, Riley Baird wrote:
>> If you could make a version of python-requests with the OpenSSL parts
>> removed, then yes. Otherwise, no.
>
> If one imports requests from Debian, OpenSSL is used.
> No idea how to prevent this.
Then as is,
On 2015-01-18 07:39, Riley Baird wrote:
> If you could make a version of python-requests with the OpenSSL parts
> removed, then yes. Otherwise, no.
If one imports requests from Debian, OpenSSL is used.
No idea how to prevent this.
> Also, if the writer of the module specifically states "w/o OpenS
On 18/01/15 05:14, W. Martin Borgert wrote:
> Hi,
>
> sorry, if this question has been discussed before.
> So far, I could not find a conclusive answer.
> Please Cc me.
>
> Python program or library "X" is licensed under GPL3+ without
> OpenSSL exception. "X" does use the python-requests library,
Hi,
sorry, if this question has been discussed before.
So far, I could not find a conclusive answer.
Please Cc me.
Python program or library "X" is licensed under GPL3+ without
OpenSSL exception. "X" does use the python-requests library,
which on load dynamically links the Python interpreter with
On Sat, 17 Jan 2015 01:58:09 + Simon McVittie wrote:
[...]
> it is entirely possible to have a
> standard that does not change or is under strict change-control, without
> having copyright infringement as a stick to hit people with. A work
> derived from a standard is not, itself, the standard
5 matches
Mail list logo
