search

progval / Limnoria

A robust, full-featured, and user/programmer-friendly Python IRC bot, with many existing plugins.
https://docs.limnoria.net/
Other
615 stars 172 forks source link

"python2 setup.py install" after a previous python3 install will actually install ~/.local/bin/supybot for python3 #551

Open o11c opened 10 years ago

o11c commented 10 years ago

Steps (with ~/.local/bin/ in $PATH):

  1. python2 setup.py install --user
  2. supybot foo.conf (runs on python2)
  3. python3 setup.py install --user
  4. supybot foo.conf (runs on python3)
  5. python2 setup.py install --user
  6. supybot foo.conf (oops, runs on python3 still!)
progval commented 10 years ago

I think that would be more a setuptools issue. I'll send them a bug report about this (unless you want to do it yourself)

o11c notifications@github.com a écrit :

Steps (with ~/.local/bin/ in $PATH):

  1. python2 setup.py install --user
  2. supybot foo.conf (runs on python2)
  3. python3 setup.py install --user
  4. supybot foo.conf (runs on python3)
  5. python2 setup.py install --user
  6. supybot foo.conf (oops, runs on python3 still!)

Reply to this email directly or view it on GitHub: https://github.com/ProgVal/Limnoria/issues/551

Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Mikaela commented 10 years ago

Is there a bug report somewhere?

jlu5 commented 9 years ago

Don't we have to delete build/ before running setup.py?

progval commented 9 years ago

@Mikaela: Hmm… I still did not, actually…

@GLolol: ????

Mikaela commented 9 years ago

@Mikaela: Hmm… I still did not, actually…

and the issue was opened in February.

Don't we have to delete build/ before running setup.py?

If you have previously installed Python 2 or 3 version, you must remove build/ before you can install Python 3 or 2 version. But I think this bug is about having to do that or at least this should be.

jlu5 commented 9 years ago

If you have previously installed Python 2 or 3 version, you must remove build/ before you can install Python 3 or 2 version. But I think this bug is about having to do that or at least this should be.

Yeah, that was what I was trying to say. Sorry for being unclear!

progval commented 4 years ago

Note: this is not a py2/py3 specific issue, it happens whenever someone switches interpreters.