Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pip install fails #5

Closed
bulletmark opened this issue Oct 10, 2013 · 3 comments
Closed

pip install fails #5

bulletmark opened this issue Oct 10, 2013 · 3 comments

Comments

@bulletmark
Copy link

I see this new repo and decided to try it. However, I get the following:

(env)pi@pi2:~/pialarm pip install pifacecommon
Downloading/unpacking pifacecommon
  Downloading pifacecommon-2.0.0.tar.gz
  Running setup.py egg_info for package pifacecommon
    Traceback (most recent call last):
      File "<string>", line 16, in <module>
      File "/home/pi/pialarm/env/build/pifacecommon/setup.py", line 54, in <module>
        long_description=open('README.md').read() + open('CHANGELOG').read(),
    IOError: [Errno 2] No such file or directory: 'README.md'
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

  File "<string>", line 16, in <module>

  File "/home/pi/pialarm/env/build/pifacecommon/setup.py", line 54, in <module>

    long_description=open('README.md').read() + open('CHANGELOG').read(),

IOError: [Errno 2] No such file or directory: 'README.md'

----------------------------------------
Cleaning up...
Command python setup.py egg_info failed with error code 1 in /home/pi/pialarm/env/build/pifacecommon
Storing complete log in /home/pi/.pip/pip.log

Can you also please add a small description of what this module is for, how it relates to the pifacedigitalio repo, and when we should use it instead of that repo?

I just want init(), read_bit(), and write_bit() with a single polled piface board so it seems to me that this repo is all I need, given the obscure comment at http://piface.github.io/pifacedigitalio/example.html refering me back to this repo?

@bulletmark
Copy link
Author

Note I changed that line to long_description="something" and the setup.py install worked,so that pwd directory issue is the only problem.

Note, subsequent to my second comment above I discovered that pifacecommon is a low level module not really relevant to me as a user, e.g. it does not even initialise the piface board, e.g. does not set the input pullups. I don't see why you publish it as (yet another) github repo. Wouldn't be less confusing to users to make this an internal private module to pifacedigitalio?

FYI, I just apt installed python-pifacedigitalio, changed my import line, and my old piface repo based code worked fine.

@tompreston
Copy link
Member

Hi, I should probably get around to removing the PyPi packages since we managed to get Debian packages sorted. Fragmentation is a problem for the user, sorry for the confusion.

Just to confirm:

sudo apt-get install python3-pifacecommon python3-pifacedigitalio

should be all you need to get everything up and running.

You're right about pifacecommon not being relevant to the user. The documentation is sparse since it's mainly a dev tool. In fact, it's due for a pretty large update (which I'm intending to push later today) which changes a lot of the functions. So I'd advice against using it until v4.0.0 is released.

The reason it's separate from pifacedigitalio is because is because pifacedigitalio isn't the only module using these common functions...

@bulletmark
Copy link
Author

Actually, to confirm back to you, an

sudo apt-get install python-pifacedigitalio

was all that was required as pifacecommon automatically gets pulled in as a dependency. I am using python 2 because some of the other modules I am using do not have python 3 compatibility. FYI, my code has been running solidly scanning inputs and writing outputs every few millisecs for many months using your old piface module. Changing that one import line from "import piface.pfio as pf" to "import pifacedigitalio as pf" is all I needed to upgrade to your latest module. Thanks for maintaining the old api!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants