top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

How best to install path.py package in Python 3.4 environment on Centos 5?

+1 vote
470 views

I want to install path.py in my Python 3.4 environment on a Centos 5 box. My /usr/local/bin/ contains: 

easy_install-3.4 
python3.4  
etc.

We are behind a proxy server and I tried this: 

# /usr/local/bin/easy_install-3.4 path.py 

Searching for path.py 
Reading https://pypi.python.org/simple/path.py/ 
Download error on https://pypi.python.org/simple/path.py/: hostname '172.29.68.1  
' doesn't match either of 'www.python.org', 'python.org', 'pypi.python.org',  
'docs.python.org', 'testpypi.python.org', 'bugs.python.org', 'wiki.python.org',  
'hg.python.org', 'mail.python.org', 'packaging.python.org', 'pythonhosted.org',  
'www.pythonhosted.org', 'test.pythonhosted.org', 'us.pycon.org', 'id.python.org' --  
Some packages may not be found!

Couldn't find index page for 'path.py' (maybe misspelled?), Am I best to use pip or easy_install? also if easy_install, how can I fix the above error?

posted Feb 23, 2015 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+3 votes
Best way to install mock package on CentOS?

What would be the best way to install mock on my Centos server? yum install mock does not recognize the
package. Have already installed 'Developer tools' using yum groupinstall.

0 votes
Django 1.5 Upgrade on CentOS

On my Mac, running python 2.7, I upgraded from 1.4 to 1.5 by doing this:

rm -rf /Library/Python/2.7/site-packages/django

Followed by python setup.py install in the dir I untar-ed Django-1.5.1 to.This all worked fine.

On a Centos system running python 2.6 I did: rm -rf /usr/lib/python2.6/site-packages/django followed by the
setup.py install. My django app is working, and appears to be running 1.5, however anytime I use manage.py (for collectstatic or syncdb or test, for example) I get these messages:

/usr/lib/python2.6/site-packages/django/core/management/__init__.py:465:
DeprecationWarning: The 'execute_manager' function is deprecated, you likely need to update your 'manage.py'; please see the Django 1.4 release notes (https://docs.djangoproject.com/en/dev/releases/1.4/).

/usr/lib/python2.6/site-packages/django/core/management/__init__.py:409:
DeprecationWarning: The 'setup_environ' function is deprecated, you likely need to update your 'manage.py'; please see the Django 1.4 release notes (https://docs.djangoproject.com/en/dev/releases/1.4/).

So it seems I still have some 1.4 stuff around. I don't get this on my Mac. How can I get rid of these messages?

0 votes
Why on CentOS, python consumes too much memory ?

Previously, we found that our python scripts consume too much memory. So I use python's resource module to restrict RLIMIT_AS's soft limit and hard limit to 200M.
On my RHEL5.3, it works OK. But on CentOS 6.2 + python2.6.6, it reports memory error(exceeding 200M). And I tested with a very small script, and result is out of my expect, it still use too much memory on my CentOS 6.2 python:
I could understand that 64 bit machines will occupy more virtual memory than that on 32 bit, because the length of some types are not the same. But I don't know why they differs so greatly(6M to 180M), Or is this only caused by that python2.6 on CentOS 6.2's memory allocation is different from python's default one? Could you kindly give me some clues?

+2 votes
CentOS 6.6 64-bit won't install on a 3 TB disk

I'm having an issue getting a C6.6 install to work on a 3 TB dual hard drive system, raid 0. I'm hoping that someone here can help.

So, I install as normal, but then reboot, and it comes to a grub prompt. Going into the system via Linux rescue, I see that most of the files dealing with the kernel haven't been installed.

I asked the maker of the server and he said that they have noticed this happen recently. A solution is to put the kernel files on a thumb drive, and then point the OS to look for them there.

I have yet to try it, but is there a better way to deal with this issue that anyone else has done?

...