Pip call with --allow-external and --allow-unverified leads to error for mysql-connector-python

X-Received	by 10.66.193.131 with SMTP id ho3mr1052537pac.42.1460016712696; Thu, 07 Apr 2016 01:11:52 -0700 (PDT)
X-Received	by 10.157.8.244 with SMTP id 107mr10979otf.14.1460016712633; Thu, 07 Apr 2016 01:11:52 -0700 (PDT)
Path	csiph.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!news.glorb.com!nt3no8539750igb.0!news-out.google.com!j7ni75igm.0!nntp.google.com!nt3no8539748igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups	de.comp.lang.python
Date	Thu, 7 Apr 2016 01:11:52 -0700 (PDT)
Complaints-To	groups-abuse@google.com
Injection-Info	glegroupsg2000goo.googlegroups.com; posting-host=212.126.162.34; posting-account=clfmUAoAAABiYOInuvhP-e_9E_8hGpyB
NNTP-Posting-Host	212.126.162.34
User-Agent	G2/1.0
MIME-Version	1.0
Message-ID	<bf753314-9be8-4487-8e63-1f7c5686da0d@googlegroups.com> (permalink)
Subject	Pip call with --allow-external and --allow-unverified leads to error for mysql-connector-python
From	schaf.mh@gmail.com
Injection-Date	Thu, 07 Apr 2016 08:11:52 +0000
Content-Type	text/plain; charset=ISO-8859-1
Xref	csiph.com de.comp.lang.python:4365

Show key headers only | View raw

HI,
over an old ansible script I did run a pip installation for the mysql-connector-python==1.0.12 (defined in the requirements.txt). (related to Django 1.5.1 installation)
This call was always executed with --allow-external and --allow-unverified and worked well.
So as you see from the version, this is a while back. If I run the same ansible playbook against a new debian installation, I run into an error.

1.) Deprication of --allow-external and --allow-unverified, telling me that they do not have any effect.
2.)Could not find version taht satisfies the requirement mysql-connector-python==1.0.12....No matching distribution found for mysql-connector-python==1.0.12.

I know that the versions are outdated (Django 1.5.1 and mysql-connector-python 1.0.12), but assume I would like to run it as it is, what would be required to get mysql-connector-python installed without --allow-external and --allow-unverified.

Do you have any hints? 
Is there a replacement for --allow-external and --allow-unverified? 
Is it still possible to run that on the newest debian, or do I have to upgrade the modules (e.g. Django, mysql,...?)

Thanks
schaf

Back to de.comp.lang.python | Previous | Next — Next in thread | Find similar

Thread

Pip call with --allow-external and --allow-unverified leads to error for mysql-connector-python schaf.mh@gmail.com - 2016-04-07 01:11 -0700
  Re: [Python-de] Pip call with --allow-external and --allow-unverified leads to error for mysql-connector-python Christopher Arndt <chris@chrisarndt.de> - 2016-04-07 14:57 +0200
    Re: [Python-de] Pip call with --allow-external and --allow-unverified leads to error for mysql-connector-python schaf.mh@gmail.com - 2016-04-07 06:30 -0700
      Re: [Python-de] Pip call with --allow-external and --allow-unverified leads to error for mysql-connector-python Christopher Arndt <chris@chrisarndt.de> - 2016-04-07 16:07 +0200
        Re: [Python-de] Pip call with --allow-external and --allow-unverified leads to error for mysql-connector-python "Marcel Hug (schaf)" <schaf.mh@gmail.com> - 2016-04-07 08:42 -0700
          Re: [Python-de] Pip call with --allow-external and --allow-unverified leads to error for mysql-connector-python Christopher Arndt <chris@chrisarndt.de> - 2016-04-07 18:10 +0200
            Re: [Python-de] Pip call with --allow-external and --allow-unverified leads to error for mysql-connector-python "Marcel Hug (schaf)" <schaf.mh@gmail.com> - 2016-04-11 05:00 -0700

csiph-web