The only thing I can think of is making sure that inside the setup.py CFLAGS
are set properly, including appropriate -I/opt/local/include and whatever
else...
Regards,
Uri
Sent from my iPhone
> On Oct 11, 2017, at 12:03, Matěj Cepl wrote:
>
>> On 2017-10-11, 12:11 GMT, Blumenthal, Uri - 0553
On 2017-10-11, 12:11 GMT, Blumenthal, Uri - 0553 - MITLL wrote:
> Unfortunately, not quite. Being pip-installable means to the
> majority of users that the package in question can be
> installed via, e.g.,
>
>pip install M2Crypto
I understand that, my question was whether you know how to ma
Unfortunately, not quite. Being pip-installable means to the majority of users
that the package in question can be installed via, e.g.,
pip install M2Crypto
Regards,
Uri
Sent from my iPhone
> On Oct 11, 2017, at 08:01, Matěj Cepl wrote:
>
>> On 2017-10-11, 11:35 GMT, Blumenthal, Uri - 055
On 2017-10-11, 11:35 GMT, Blumenthal, Uri - 0553 - MITLL wrote:
> And it is not installable via PIP, though to me being placed
> on pypi site suggested that it should be (that's how I tried
> to install it).
What’s needed for package to be pip installable? I would think
that if
python setu
And it is not installable via PIP, though to me being placed on pypi site
suggested that it should be (that's how I tried to install it).
Regards,
Uri
Sent from my iPhone
> On Oct 11, 2017, at 06:55, Richard Levitte wrote:
>
> I got curious and decided to take a look, and well, it appears
> s
I got curious and decided to take a look, and well, it appears
setup.py has issues. I posted an issue in gitlab about it:
https://gitlab.com/m2crypto/m2crypto/issues/184
In message on Wed, 11 Oct 2017
08:12:38 +0200, Matěj Cepl said:
mcepl> On 2017-10-10, 21:17 GMT, Blumenthal, Uri - 0553 -
