Problem installing SuRF package using pip

[Tatiana Al-Chueyr Martins]

Hello guys!

I managed to install SuRF using:

$ easy_install -U surf

$ easy_install -U surf.sparql_protocol

$ easy_install -U surf.rdflib

Installing from the source also succeeded, by checking out the source from master [1] and runing:

$ python setup.py install

However, while trying to install SuRF via pip, I got an IOError, presented bellow. This happened both on Python2.7 and Python2.6, with or without virtualenv.

######

$ pip install surf

Downloading/unpacking surf

  Downloading surf-doc_1.1.4.zip (396Kb): 396Kb downloaded

  Running setup.py egg_info for package surf

    Traceback (most recent call last):

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

    IOError: [Errno 2] No such file or directory: '/home/tati_alchueyr/.virtualenvs/surf/build/surf/setup.py'

    Complete output from command python setup.py egg_info:

    Traceback (most recent call last):

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

IOError: [Errno 2] No such file or directory: '/home/tati_alchueyr/.virtualenvs/surf/build/surf/setup.py'

----------------------------------------

Command python setup.py egg_info failed with error code 1 in /home/tati_alchueyr/.virtualenvs/surf/build/surf

Storing complete log in /home/tati_alchueyr/.pip/pip.log

######

Could this be related to these lines, at setup.py?

#try:

#    from setuptools import setup, find_packages

#except ImportError:

from ez_setup import use_setuptools

Best regards,

Tatiana

[1] http://surfrdf.googlecode.com/

[Christoph Burgmer]

Hi Tatiana,

the issue is known and filed under http://code.google.com/p/surfrdf/issues/detail?id=45.

The issues seems to stem from pip downloading the documentation of SuRF instead of the source code which in addition comes from pip strictly following the Python naming conventions, that SuRF should try to follow.

As far as I remember, fixing the bug would mean renaming some of the packages, which would break the API. So nothing that should be done in a minor release I guess :)
-Christoph

[Tatiana Al-Chueyr Martins]

Hi Christoph!

[CUT]

On Friday, June 22, 2012 2:33:21 PM UTC-3, Christoph Burgmer wrote:

Hi Tatiana,

the issue is known and filed under http://code.google.com/p/surfrdf/issues/detail?id=45.

Ok, sorry, we'll look up there before reporting here ;)

 

The issues seems to stem from pip downloading the documentation of SuRF instead of the source code which in addition comes from pip strictly following the Python naming conventions, that SuRF should try to follow.

As far as I remember, fixing the bug would mean renaming some of the packages, which would break the API. So nothing that should be done in a minor release I guess :)

I'll have a look on it as well, if you don't mind. What's the best way to contribute to SuRF? Sending patches to the mailing list, sending patches using Google Code's issues system or pull requests on GitHub?

I should use SuRF at my company and would like to contribute somehow.

Regards,

Tatiana

 

-Christoph

[Christoph Burgmer]

On Saturday, June 23, 2012 3:57:43 AM UTC+2, Tatiana Al-Chueyr Martins wrote:

...
 

I'll have a look on it as well, if you don't mind. What's the best way to contribute to SuRF? Sending patches to the mailing list, sending patches using Google Code's issues system or pull requests on GitHub?

I should use SuRF at my company and would like to contribute somehow.

So far I guess the best thing is to send patches, probably attached to a bug report, maybe creating a new one for a new issue.

I saw you forked my private clone of SuRF on GitHub. I currently can't keep the repo up to date with the SVN, my machine that was doing the synching is offline. So you should work with the svn repository here.

I think it is a good time to discuss whether we want to host the source code on GitHub instead of the SVN here. Some projects (e.g. PhantomJS) use most of the infrastructure here while moving the code to GitHub. That means of course that everybody would then need to use Git.

-Christoph

[Tatiana Al-Chueyr Martins]

Hi Christoph!

[cut] 

So far I guess the best thing is to send patches, probably attached to a bug report, maybe creating a new one for a new issue.

I saw you forked my private clone of SuRF on GitHub. I currently can't keep the repo up to date with the SVN, my machine that was doing the synching is offline. So you should work with the svn repository here.

Ok.

 

I think it is a good time to discuss whether we want to host the source code on GitHub instead of the SVN here. Some projects (e.g. PhantomJS) use most of the infrastructure here while moving the code to GitHub. That means of course that everybody would then need to use Git.

I believe using GitHub could improve managing contributions and save you some time... But the decision is up to the community ;)

Regards,

Tatiana

 

-Christoph

[Tatiana Al-Chueyr Martins]

Guys,

I've just built a SuRF package based on the trunk (r374), using:

- python setup.py sdist

And uploaded to a internal Chishop 0.2.0:

- python setup.py sdist upload -r <internal-chishop>

After this, I was successful installing SuRF using pip:

- pip install surf --index-url=http://pypi.<internal-chishop>.com

This happened using:

- cPython 2.6.1

- setuptools==0.6c11

Is issue #45 still open?

- http://code.google.com/p/surfrdf/issues/detail?id=45

Regards,

Tatiana