search

z3z1ma / dbt-osmosis

Provides automated YAML management, a dbt server, streamlit workbench, and git-integrated dbt model output diff tools
https://z3z1ma.github.io/dbt-osmosis/
Apache License 2.0
422 stars 45 forks source link

pip install dbt-osmosis installs version 0.5.0 #62

Closed roshanabady closed 1 year ago

roshanabady commented 1 year ago

Using pip install dbt-osmosis doesn't install the latest version. I even tried pip install dbt-osmosis==0.11.17 but pip errored out. I downloaded the package and installed from source. image

MarekVigas commented 1 year ago

Looks like the only problem is with too strict/explicit Python version requirements. If you are running Python version > 3.11 you can install with pip install --ignore-requires-python dbt-osmosis==0.11.17

z3z1ma commented 1 year ago

The version constraint in the most recent release is relaxed to accept py311 I wouldn't have the constraint at all but one of the dependencies, ydata requires the constraint.

https://github.com/z3z1ma/dbt-osmosis/releases/tag/v0.11.19

Version 0.11.9 on pypi too should be fine.

z3z1ma commented 1 year ago

It requires an extra. It’s in the docs.

pip install dbt-osmosis[workbench]

On Wed, Jun 28, 2023 at 10:23 PM Sam Bradbury @.***> wrote:

I installed 0.11.17 as mentioned above and as expected the error mentioned here https://github.com/z3z1ma/dbt-osmosis/issues/53 went away.

Then upon running dbt-osmosis workbench I ran into a number of missing package errors. I manually installed feedparser andydata_profiling but then finally ran into AttributeError: 'Flags' object has no attribute 'PROFILE'

If anyone has a combination of versions that work together please post here. I'd love to get osmosis running but at this point have spent many hours with little progress.

— Reply to this email directly, view it on GitHub https://github.com/z3z1ma/dbt-osmosis/issues/62#issuecomment-1612379261, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ2N4CYAVDL5T6Y7BMHNEJ3XNTYLNANCNFSM6AAAAAAXKNUHUA . You are receiving this because you modified the open/close state.Message ID: @.***>