-
-
Notifications
You must be signed in to change notification settings - Fork 525
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
Cannot install Panel for development as it cannot resolve dependencies #945
Comments
This comment has no answers in it, so please feel free to skip if you just want an answer! (Minor note: you say "I'm running Back in mid-November, I tried to set up a panel development environment on a new machine running ubuntu. I was using conda 4.7.12 and wanted a python 3.7 environment (I was not using doit, although that shouldn't make a difference). I had the same kind of problem as you - seemingly endless conda solving (session notes below, at the end). I unfortunately did not have time to investigate, so I set up my development environment without using conda. If I had time, I would probably try: reducing number of channels; pinning some package versions; setting channel priority to strict; installing part of the environment first and then adding to it. Hopefully someone will have a better suggestion. You can see that on travis-ci (ubuntu) with python 3.6, the develop install step is currently taking around 4 minutes: https://travis-ci.org/holoviz/panel/jobs/636706333#L878. I believe the main developers all use mac, so it's presumably working fine there. I think windows testing of panel was unfortunately dropped some time ago. (At the end of last year, I did try to set up appveyor/windows again, but I was not able to log in as there is some email account problem. We would probably like to set up github actions (holoviz-dev/pyctdev#65), but need to find time to do it.) From mid-November 2019... If I try to install panel's "recommended", "tests", and "build" dependencies with conda 4.7.12 in a clean python 3.7 environment, my ubuntu machine's fans all come on and I eventually kill it...
|
This is quite worrying, I wonder why Travis is managing to solve the env okay but your local machines aren't. |
Note that I was talking about a python 3.7 environment. A python 3.6 environment worked for me (as it does on travis), but I needed python 3.7. In both cases I was using ubuntu. @MarcSkovMadsen has the problem with both python 3.6 and 3.7. He's using windows. |
Just checked and the situation appears to be the same for me still:
|
Don't know how useful this is, but removing both the vtk and pytest-cov pins allowed conda to solve the environment (python 3.7, linux). Removing only one of them (either of them) didn't help.
|
Interesting, I'll try to open a PR which unpins these and see if I can get tests passing without the pins. |
@MarcSkovMadsen: If you get time, would you be able to re-try on Windows? While @philippjfr's changes updates will likely have fixed linux/3.7, it's not obvious to me how we know the development environment can be set up on windows. Thanks! |
FYI @ceball and others The installation can now run without errors for me on Windows 8.1 and with python 3.7. FYI. I get the below warning from ...
Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... b'Enabling notebook extension jupyter-js-widgets/extension...\n - Validating: ok\n'
done
Obtaining file:///C:/repos/private/panel
Installing build dependencies: started
Installing build dependencies: still running...
Installing build dependencies: finished with status 'done'
WARNING: Missing build requirements in pyproject.toml for file:///C:/repos/private/panel.
WARNING: The project does not specify a build backend, and pip cannot fall back to setuptools without 'wheel'.
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Installing backend dependencies: started
Installing backend dependencies: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'done'
Installing collected packages: panel
Found existing installation: panel 0.7.1a2
Uninstalling panel-0.7.1a2:
Successfully uninstalled panel-0.7.1a2
Running setup.py develop for panel
Successfully installed panel I finally ran (panel_dev) C:\repos\private\panel>pip install -e .
Obtaining file:///C:/repos/private/panel
Installing build dependencies ... done
WARNING: Missing build requirements in pyproject.toml for file:///C:/repos/private/panel.
WARNING: The project does not specify a build backend, and pip cannot fall back to setuptools without 'wheel'.
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing wheel metadata ... done
Requirement already satisfied: pyviz-comms>=0.7.2 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site
-packages (from panel==0.7.1a2.post35+gcae7f46) (0.7.2)
Requirement already satisfied: bokeh>=1.4.0 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-packa
ges (from panel==0.7.1a2.post35+gcae7f46) (1.4.0)
Requirement already satisfied: pyct>=0.4.4 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-packag
es (from panel==0.7.1a2.post35+gcae7f46) (0.4.6)
Requirement already satisfied: param>=1.9.0 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-packa
ges (from panel==0.7.1a2.post35+gcae7f46) (1.9.2)
Requirement already satisfied: markdown in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-packages
(from panel==0.7.1a2.post35+gcae7f46) (3.1.1)
Requirement already satisfied: python-dateutil>=2.1 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\si
te-packages (from bokeh>=1.4.0->panel==0.7.1a2.post35+gcae7f46) (2.8.1)
Requirement already satisfied: tornado>=4.3 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-packa
ges (from bokeh>=1.4.0->panel==0.7.1a2.post35+gcae7f46) (6.0.3)
Requirement already satisfied: PyYAML>=3.10 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-packa
ges (from bokeh>=1.4.0->panel==0.7.1a2.post35+gcae7f46) (5.2)
Requirement already satisfied: six>=1.5.2 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-package
s (from bokeh>=1.4.0->panel==0.7.1a2.post35+gcae7f46) (1.13.0)
Requirement already satisfied: numpy>=1.7.1 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-packa
ges (from bokeh>=1.4.0->panel==0.7.1a2.post35+gcae7f46) (1.17.5)
Requirement already satisfied: packaging>=16.8 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-pa
ckages (from bokeh>=1.4.0->panel==0.7.1a2.post35+gcae7f46) (20.0)
Requirement already satisfied: pillow>=4.0 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-packag
es (from bokeh>=1.4.0->panel==0.7.1a2.post35+gcae7f46) (5.4.1)
Requirement already satisfied: Jinja2>=2.7 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-packag
es (from bokeh>=1.4.0->panel==0.7.1a2.post35+gcae7f46) (2.10.3)
Requirement already satisfied: setuptools>=36 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-pac
kages (from markdown->panel==0.7.1a2.post35+gcae7f46) (45.1.0.post20200119)
Requirement already satisfied: pyparsing>=2.0.2 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-p
ackages (from packaging>=16.8->bokeh>=1.4.0->panel==0.7.1a2.post35+gcae7f46) (2.4.6)
Requirement already satisfied: MarkupSafe>=0.23 in c:\users\masma\appdata\local\continuum\anaconda3\envs\panel_dev\lib\site-p
ackages (from Jinja2>=2.7->bokeh>=1.4.0->panel==0.7.1a2.post35+gcae7f46) (1.1.1)
Installing collected packages: panel
Found existing installation: panel 0.7.1a2.post35+gcae7f46
Uninstalling panel-0.7.1a2.post35+gcae7f46:
Successfully uninstalled panel-0.7.1a2.post35+gcae7f46
Running setup.py develop for panel
Successfully installed panel |
That's good; thanks for taking the time to check and report back @MarcSkovMadsen
I assume you are talking about this:
Thanks for reporting it. It's ok to ignore for now. @a-recknagel has previously reported it, and even made a fix (which is to declare that the build backend is setuptools), but we just needed to figure out the consequences/extra requirements. Probably it's just requiring a newer version of setuptools than we state at present, but we need to check and test that ("we" being anyone who gets the time...).
That command was actually already run as the last step of your "doit develop_install" command, so the final pip install command is redundant at that stage. I believe we noted this in a panel issue, but I don't seem to see that issue any more. Personally, if I were using conda to install all the dependencies, and pip to do the editable install of Panel itself, then I would use |
I would like to start to contribute to Panel and thus I am following the Developer Guide at https://panel.holoviz.org/developer_guide/index.html to get up and running. And as the there are some issues regarding the developer guide I'm also mixin in details from #866.
I'm developing on Windows 8.1. Hopefully I will soon be on Windows 10.
I'm running
doit env_create -c pyviz/label/dev -c conda-forge -c bokeh --name=panel_dev --python=3.6
but now it's just been running for 2.5 hours trying to resolve dependencies and it seems dead. I tried yesterday withpython=3.7
and that was the same experience.As I'm not normally using conda I don't know how to solve this problem.
Please help.
Thanks.
The text was updated successfully, but these errors were encountered: