-
Notifications
You must be signed in to change notification settings - Fork 3k
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 from git url doesn't honour setup.cfg #1630
Comments
Could you say what version setuptools you are using? I believe this might be a bug where it is not reading your project's setup.cfg when doing an editable install. Pip never does any of the actual installing, it tells setuptools to. |
Maybe 0.6.24? Not sure as:
|
Firstly, you may like to check whether a setup.cfg exists in your current directory, as it may override the project's setup.cfg. This may be a legimate bug in distribute 0.6.24 (virtually unmaintained now), however you might like to try as a workaround upgrading to newer versions of the packaging tools. I'm on windows atm, so can't test compiling, but to upgrade them on your system would want to run
(outside a virtualenv), you could even just update your particular virtualenv's copies of pip & setuptools inside that environment, i.e
If this behaviour is still present using the newest tools then this might be considered a bug in setuptools. |
Tested with pip 1.5.4, setuptools 3.1, virtualenv 1.11.4: same problem. This is enough to reproduce:
|
pypa/pip#1630 Fixes ticket #18 (opened in 2010!)
I've worked around this bug by passing manually the defines found in the setup.cfg to the Extension (reading the cfg files works ok in the setup.py: it's the Extension object that doesn't receive them). If you want to test please use an older commit, for instance:
|
pypa/pip#1630 Fixes ticket #18 (opened in 2010!)
pypa/pip#1630 Fixes ticket #18 (opened in 2010!) Conflicts: NEWS
What's new in psycopg 2.5.3 ^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Work around `pip issue #1630 <https://github.com/pypa/pip/issues/1630>`__ making installation via ``pip -e git+url`` impossible (:ticket:`#18`). - Copy operations correctly set the `cursor.rowcount` attribute (:ticket:`#180`). - It is now possible to call `get_transaction_status()` on closed connections. - Fixed unsafe access to object names causing assertion failures in Python 3 debug builds (:ticket:`#188`). - Mark the connection closed if found broken on `poll()` (from 🎫`#192` discussion) - Fixed handling of dsn and closed attributes in connection subclasses failing to connect (from 🎫`#192` discussion). - Added arbitrary but stable order to `Range` objects, thanks to Chris Withers (:ticket:`#193`). - Avoid blocking async connections on connect (:ticket:`#194`). Thanks to Adam Petrovich for the bug report and diagnosis. - Don't segfault using poorly defined cursor subclasses which forgot to call the superclass init (:ticket:`#195`). - Mark the connection closed when a Socket connection is broken, as it happens for TCP connections instead (:ticket:`#196`). - Fixed overflow opening a lobject with an oid not fitting in a signed int (:ticket:`#203`). - Fixed handling of explicit default ``cursor_factory=None`` in `connection.cursor()` (:ticket:`#210`). - Fixed possible segfault in named cursors creation. - Fixed debug build on Windows, thanks to James Emerton.
What's new in psycopg 2.5.3 ^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Work around `pip issue #1630 <https://github.com/pypa/pip/issues/1630>`__ making installation via ``pip -e git+url`` impossible (:ticket:`#18`). - Copy operations correctly set the `cursor.rowcount` attribute (:ticket:`#180`). - It is now possible to call `get_transaction_status()` on closed connections. - Fixed unsafe access to object names causing assertion failures in Python 3 debug builds (:ticket:`#188`). - Mark the connection closed if found broken on `poll()` (from 🎫`#192` discussion) - Fixed handling of dsn and closed attributes in connection subclasses failing to connect (from 🎫`#192` discussion). - Added arbitrary but stable order to `Range` objects, thanks to Chris Withers (:ticket:`#193`). - Avoid blocking async connections on connect (:ticket:`#194`). Thanks to Adam Petrovich for the bug report and diagnosis. - Don't segfault using poorly defined cursor subclasses which forgot to call the superclass init (:ticket:`#195`). - Mark the connection closed when a Socket connection is broken, as it happens for TCP connections instead (:ticket:`#196`). - Fixed overflow opening a lobject with an oid not fitting in a signed int (:ticket:`#203`). - Fixed handling of explicit default ``cursor_factory=None`` in `connection.cursor()` (:ticket:`#210`). - Fixed possible segfault in named cursors creation. - Fixed debug build on Windows, thanks to James Emerton.
What's new in psycopg 2.5.3 ^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Work around `pip issue #1630 <https://github.com/pypa/pip/issues/1630>`__ making installation via ``pip -e git+url`` impossible (:ticket:`#18`). - Copy operations correctly set the `cursor.rowcount` attribute (:ticket:`#180`). - It is now possible to call `get_transaction_status()` on closed connections. - Fixed unsafe access to object names causing assertion failures in Python 3 debug builds (:ticket:`#188`). - Mark the connection closed if found broken on `poll()` (from 🎫`#192` discussion) - Fixed handling of dsn and closed attributes in connection subclasses failing to connect (from 🎫`#192` discussion). - Added arbitrary but stable order to `Range` objects, thanks to Chris Withers (:ticket:`#193`). - Avoid blocking async connections on connect (:ticket:`#194`). Thanks to Adam Petrovich for the bug report and diagnosis. - Don't segfault using poorly defined cursor subclasses which forgot to call the superclass init (:ticket:`#195`). - Mark the connection closed when a Socket connection is broken, as it happens for TCP connections instead (:ticket:`#196`). - Fixed overflow opening a lobject with an oid not fitting in a signed int (:ticket:`#203`). - Fixed handling of explicit default ``cursor_factory=None`` in `connection.cursor()` (:ticket:`#210`). - Fixed possible segfault in named cursors creation. - Fixed debug build on Windows, thanks to James Emerton.
What's new in psycopg 2.5.3 ^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Work around `pip issue #1630 <https://github.com/pypa/pip/issues/1630>`__ making installation via ``pip -e git+url`` impossible (:ticket:`#18`). - Copy operations correctly set the `cursor.rowcount` attribute (:ticket:`#180`). - It is now possible to call `get_transaction_status()` on closed connections. - Fixed unsafe access to object names causing assertion failures in Python 3 debug builds (:ticket:`#188`). - Mark the connection closed if found broken on `poll()` (from 🎫`#192` discussion) - Fixed handling of dsn and closed attributes in connection subclasses failing to connect (from 🎫`#192` discussion). - Added arbitrary but stable order to `Range` objects, thanks to Chris Withers (:ticket:`#193`). - Avoid blocking async connections on connect (:ticket:`#194`). Thanks to Adam Petrovich for the bug report and diagnosis. - Don't segfault using poorly defined cursor subclasses which forgot to call the superclass init (:ticket:`#195`). - Mark the connection closed when a Socket connection is broken, as it happens for TCP connections instead (:ticket:`#196`). - Fixed overflow opening a lobject with an oid not fitting in a signed int (:ticket:`#203`). - Fixed handling of explicit default ``cursor_factory=None`` in `connection.cursor()` (:ticket:`#210`). - Fixed possible segfault in named cursors creation. - Fixed debug build on Windows, thanks to James Emerton.
Closing this, if it continues to happen please reopen this issue or open a new one with reproduction steps, however at this time I cannot reproduce this even with older commit. |
It seems working fine as of pip 9.0.1, setuptools 34.3.2, virtualenv 15.1.0, thank you. |
Trying to install psycopg from a git url fails in an apparently mysterious way:
The reason of the failure is apparently that the gcc command line is missing a few declarations that are defined in the
setup.cfg
. Installing by any other mean (downloading or just withpip install psycopg2
) also adds the following declarations to the command line:If you suggest an acceptable way to work around this problem fixing the setup.py we'd be happy to implement it in psycopg.
Tested pip version is 1.5.2
The text was updated successfully, but these errors were encountered: