Package Details: python-dash 2.15.0-1

Git Clone URL: https://aur.archlinux.org/python-dash.git (read-only, click to copy)
Package Base: python-dash
Description: A python framework for building analytical web applications
Upstream URL: https://plot.ly/products/dash/
Licenses: MIT
Conflicts: python-dash-core-components, python-dash-html-components, python-dash-renderer, python-dash-table
Provides: python-dash-core-components, python-dash-html-components, python-dash-renderer, python-dash-table
Submitter: thrasibule
Maintainer: thrasibule
Last Packager: thrasibule
Votes: 5
Popularity: 0.000000
First Submitted: 2017-07-11 17:38 (UTC)
Last Updated: 2024-02-16 15:34 (UTC)

Latest Comments

1 2 Next › Last »

aeonik commented on 2023-09-27 19:40 (UTC)

This is a diff that can be used to make this PKGBUILD up to date:

5c5
< pkgver=2.13.0
---
> pkgver=2.3.1
17c17
< sha256sums=('07c192db694b9bb4c87d57b6da877413f2695bfcb1d5c51f08995de7dcdd1e92')
---
> sha256sums=('07f59e2ebec62c9123a8d8ccfd9c57c73095080b5cbfb3bb44f27ce0b228b4ef')

jorgicio commented on 2021-10-08 15:22 (UTC)

Yes, I confirm that python-dash-renderer is also merged here, so it also should be added as a provided and conflict package.

thrasibule commented on 2021-10-06 16:11 (UTC)

@greyltc missed that one! I've submitted a request for python-dash-renderer as well.

greyltc commented on 2021-10-06 11:28 (UTC)

@thrasibule thanks! that did the trick. I guess upstream's docs are out of date (despite them actually saying they're up to date as of the 2.0 release).

I've submitted a deletion request for my python-dash-table AUR package. Looks like your python-dash-renderer is rolled into this now too. Shall we ask for that to be deleted too?

thrasibule commented on 2021-10-05 16:49 (UTC)

dash_core_components has been moved inside dash, so you need to to something like that instead:

from dash import dcc

Same for dash_table or html.

greyltc commented on 2021-10-05 08:28 (UTC)

A recent update here seems to have broken my stuff. I can no longer access core components for example. Here's the docs on how core components should be imported: https://dash.plotly.com/dash-core-components

But import dash_core_components as dcc gives "ModuleNotFoundError: No module named 'dash_core_components'"

Am I doing something wrong?

jorgicio commented on 2021-09-22 22:04 (UTC) (edited on 2021-09-22 22:05 (UTC) by jorgicio)

As of 2.0.0 version of this package, core-components, html-components and table are merged into the same package. So you may consider adding these lines to the PKGBUILD:

provides=('python-dash' 'python-dash-core-components' 'python-dash-html-components' 'python-dash-table')

conflicts=('python-dash-core-components' 'python-dash-html-components' 'python-dash-table')

And the split packages won't be required anymore.

greyltc commented on 2020-08-02 14:43 (UTC)

great! I'm happy to take a crack at making the initial split package version too if you'd rather that. Just let me know!

thrasibule commented on 2020-08-02 13:13 (UTC)

@greyltc, that makes sense. I'll try to post a split version today, and add you as co-maintainer.

greyltc commented on 2020-08-02 09:01 (UTC) (edited on 2020-08-02 09:01 (UTC) by greyltc)

@thrasibule, what do you think about combining all the following into one split package that you and I could co-maintain together?  
python-dash  
python-dash-table  
python-dash-core-components  
python-dash-renderer (soon to be obsolete apparently)  
python-dash-daq  
python-dash-html-components  
I think these are all so tightly integrated with eachother that it doesn't make sense to package them all separately.

1 2 Next › Last »