Clean install doesn't work under python2.7

[pennucci]

Not sure it was the intention given the imminent sunset, but I just tried a clean install of pint under python 2.7 and I get an error "error: 'egg_base' must be a directory name (got src)", which looks related to: pypa/setuptools#1136

i.e., python2 vs python3, but elsewhere I read this might be a setuptools problem.

[scottransom]

@pennucci For me, at least, this was fixed by making sure that I was using up-to-date versions of both setuptools and pip.

[pennucci]

Ah! I updated pip, but not setuptools. That worked. Thanks!

[aarchiba]

This specific error is discussed in the current version of the docs. Did you see that? Were the instructions there sufficient? Anne

…

On Tue., Oct. 22, 2019, 17:01 Tim Pennucci, ***@***.***> wrote: Closed #566 <#566>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#566?email_source=notifications&email_token=AABBNIY3HDQYVOKUXVAHEJLQP4PXDA5CNFSM4JDRUAZ2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOULZ7AQA#event-2733895744>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABBNI2CGSMGVQXKCUECTSTQP4PXDANCNFSM4JDRUAZQ> .

[pennucci]

I had not looked in the docs; it wasn't too long ago that I had successfully re-installed pint from scratch with no issue, and given the large number of recent changes I had assumed that the issue may have arisen from them.  Based on that, I didn't even think to look at the docs.  In short, it was my lack of due diligence; apologies!

…

On 10/23/19 00:40, Anne Archibald wrote: This specific error is discussed in the current version of the docs. Did you see that? Were the instructions there sufficient? Anne On Tue., Oct. 22, 2019, 17:01 Tim Pennucci, ***@***.***> wrote: > Closed #566 <#566>. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#566?email_source=notifications&email_token=AABBNIY3HDQYVOKUXVAHEJLQP4PXDA5CNFSM4JDRUAZ2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOULZ7AQA#event-2733895744>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AABBNI2CGSMGVQXKCUECTSTQP4PXDANCNFSM4JDRUAZQ> > . > — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#566?email_source=notifications&email_token=AANPWISYZNLQLF42BWLU3G3QP56MDA5CNFSM4JDRUAZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB7OEBI#issuecomment-545186309>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANPWITNEEVBQLK3ZGHIYWLQP56MDANCNFSM4JDRUAZQ>.

[aarchiba]

No worries! I'm just trying to evaluate how effective the new docs and their structure are. Anne

…

On Wed, 23 Oct 2019 at 10:51, Tim Pennucci ***@***.***> wrote: I had not looked in the docs; it wasn't too long ago that I had successfully re-installed pint from scratch with no issue, and given the large number of recent changes I had assumed that the issue may have arisen from them. Based on that, I didn't even think to look at the docs. In short, it was my lack of due diligence; apologies! On 10/23/19 00:40, Anne Archibald wrote: > This specific error is discussed in the current version of the docs. Did > you see that? Were the instructions there sufficient? > > Anne > > On Tue., Oct. 22, 2019, 17:01 Tim Pennucci, ***@***.***> > wrote: > > > Closed #566 <#566>. > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > > < #566?email_source=notifications&email_token=AABBNIY3HDQYVOKUXVAHEJLQP4PXDA5CNFSM4JDRUAZ2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOULZ7AQA#event-2733895744 >, > > or unsubscribe > > > < https://github.com/notifications/unsubscribe-auth/AABBNI2CGSMGVQXKCUECTSTQP4PXDANCNFSM4JDRUAZQ > > > . > > > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub > < #566?email_source=notifications&email_token=AANPWISYZNLQLF42BWLU3G3QP56MDA5CNFSM4JDRUAZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB7OEBI#issuecomment-545186309>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AANPWITNEEVBQLK3ZGHIYWLQP56MDANCNFSM4JDRUAZQ >. > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#566?email_source=notifications&email_token=AABBNIZA6LF4HNXFJYUJ46LQQANBZA5CNFSM4JDRUAZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECAZSYQ#issuecomment-545364322>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABBNI4WFEU3HEPTSQN3YTTQQANBZANCNFSM4JDRUAZQ> .