watson-developer-cloud/python-sdk

AssertionError when Pip installing sdk in DSX

tylernd27 opened this issue · 9 comments

tylernd27 commented

Expected behavior

Install with no issue.

Actual behavior

AssertionError

Steps to reproduce the problem

!pip install --upgrade watson-developer-cloud in DSX

Code snippet (Note: Do not paste your credentials)

AssertionError: Multiple .dist-info directories: /gpfs/fs01/user/sd8e-783f77b5534e01-6650b5108aaf/.local/lib/python3.5/site-packages/zope.interface-4.4.3.dist-info, /gpfs/fs01/user/sd8e-783f77b5534e01-6650b5108aaf/.local/lib/python3.5/site-packages/zope.interface-4.4.2.dist-info

python sdk version

all, but specifically happened first when running !pip install --upgrade watson-developer-cloud==1.0.1

python version

3.5

ehdsouza commented

This issue was reproducible in DSX. Restarting the kernel resolved it.

tylernd27 commented

after restarting kernel did not work --- ran !pip install --upgrade pip, restarted kernel and it resolved it.

  • 👍2
ammardodin commented

@tylernd27 I don't believe this is an issue with the wdc package. Looking at the errors above, I believe the problem here is that it appears that DSX specifies a custom build directory for pip. pip doesn't actively manage custom build directories, since those are usually used for incremental build optimizations. As such, that responsibility becomes the burden of the user, which in this case is DSX. I assume running !pip install --upgrade pip and restarting the kernel has triggered the deletion of those custom build directories, which is probably why you didn't see the error above anymore.

I've attempted to reproduce the issue in the latest release of DSX now Watson Studio, and I was unsuccessful 😞 , so maybe it has been addressed 🤞 . Can you perhaps try reproducing the issue in a new notebook now and see if the issue still persists ?

  • 👍1
tylernd27 commented

I can reproduce the error when I rollback the sdk version in DSX. So if I upgrade to latest, restart kernel, then run !pip install --upgrade watson-developer-cloud==1.0.1 or any previous version.

ammardodin commented

Interesting... So I just tried the following:

  1. Create a notebook in DSX
  2. Run !pip install --upgrade watson-developer-cloud
  3. Restart the kernel
  4. Run !pip install --upgrade watson-developer-cloud==1.0.0

I wasn't able to reproduce the error above... @ehdsouza Can you try when you get a chance ?

tylernd27 commented

Can you try 1.0.1? my assumption that all previous versions would not work may be wrong. I just tried with 1.0.0 and it worked, but 1.0.1 did not

ammardodin commented

Interesting, I tried the following:

  1. Create a notebook in DSX
  2. Run !pip install --upgrade watson-developer-cloud
  3. Restart the kernel
  4. Run !pip install --upgrade watson-developer-cloud==1.0.1

I didn't see the error above when rolling back on 1.0.1 from the latest 🤔

  • 😕4
ehdsouza commented

I tried to reproduce the issue in DSX but couldn't. Seems like the issue is fixed on DSX side. Anyone facing the issue, could try:

  1. !pip install --upgrade pip
  2. Restarting the kernel