2 ms·

Really? Does it resolve and install libpq-dev or postgresql-libs when you try to install psycopg2? Or even tell you that you need to install them? The problem

Really? Does it resolve and install libpq-dev or postgresql-libs when you try to install psycopg2? Or even tell you that you need to install them? The problem isn't that this can't be solved in a consistent, clear way. The problem is that nobody views this as their problem to solve.

ubernostrum 10y ago
It also doesn't install Postgres itself, doesn't install a TCP/IP stack or any type of socket abstraction for communicating with a Postgres server, doesn't display an interactive SQL tutorial to ensure I'll know what to do once I get it running, doesn't install an operating system capable of running the psql client, and doesn't go out and buy me a computer or sign up a cloud hosting account with a provisioned database. Would you fault it for those, too? Or would you find a point where you declare "not my problem", and then open yourself up to precisely this same criticism, just with the line drawn in a different place than where it currently is? I'm OK with the fact that the Python package installer installs Python packages. I'm OK with the fact that glancing at the documentation for psycopg immediately tells me up-front in its install instructions the things I'll need. It also helpfully pre-empts the article here, suggesting a final debugging step for a non-functioning install: Complain on your blog or on Twitter that psycopg2 is the worst package ever and about the quality time you have wasted figuring out the correct ARCHFLAGS. Especially useful from the Starbucks near you.
- crdoconnor 10y ago
  >It also doesn't install Postgres itself Not a dependency. >doesn't install a TCP/IP stack or any type of socket abstraction for communicating with a Postgres server Because that's never caused a problem when installing psycopg2, ever. >doesn't display an interactive SQL tutorial Not a dependency. >doesn't install an operating system capable How exactly would you be running pip without an OS? >Would you fault it for those, too? I think you misunderstand what a dependency actually is.

ubernostrum 10y ago

It also doesn't install Postgres itself, doesn't install a TCP/IP stack or any type of socket abstraction for communicating with a Postgres server, doesn't display an interactive SQL tutorial to ensure I'll know what to do once I get it running, doesn't install an operating system capable of running the psql client, and doesn't go out and buy me a computer or sign up a cloud hosting account with a provisioned database. Would you fault it for those, too? Or would you find a point where you declare "not my problem", and then open yourself up to precisely this same criticism, just with the line drawn in a different place than where it currently is? I'm OK with the fact that the Python package installer installs Python packages. I'm OK with the fact that glancing at the documentation for psycopg immediately tells me up-front in its install instructions the things I'll need. It also helpfully pre-empts the article here, suggesting a final debugging step for a non-functioning install: Complain on your blog or on Twitter that psycopg2 is the worst package ever and about the quality time you have wasted figuring out the correct ARCHFLAGS. Especially useful from the Starbucks near you.

crdoconnor 10y ago
>It also doesn't install Postgres itself Not a dependency. >doesn't install a TCP/IP stack or any type of socket abstraction for communicating with a Postgres server Because that's never caused a problem when installing psycopg2, ever. >doesn't display an interactive SQL tutorial Not a dependency. >doesn't install an operating system capable How exactly would you be running pip without an OS? >Would you fault it for those, too? I think you misunderstand what a dependency actually is.