Ok this was due to an install of miniconda then choosing to unconditionally
install an older version of cryptography.
> On Feb 10, 2021, at 3:40 PM, Robert Nicholson
> wrote:
>
> Just reinstalling cryptography with pip install seems to have fixed my issue.
>
> Any pointer
Just reinstalling cryptography with pip install seems to have fixed my issue.
Any pointers on why?
> On Feb 10, 2021, at 3:21 PM, Robert Nicholson
> wrote:
>
> I’m using Python 3.7.0
>
> so I have multiple environments all on the same architecture with the same
>
I’m using Python 3.7.0
so I have multiple environments all on the same architecture with the same
python release using anonconda.
What I discovered was that if I install the cryptography module in my dev / uat
and then tried to synchronize to production server using rsync I ended up with
error