installing `0.6.0` seems to work fine using pip bu...
# announcements
d
installing
0.6.0
seems to work fine using pip but getting some interesting errors when trying to install via pipenv:
Pipfile is pretty straightforward. Looks like the following:
Copy code
[[source]]
url = "<https://pypi.org/simple>"
verify_ssl = true
name = "pypi"

[packages]
dagster = "==0.6.0.post0"
dagit = "==0.6.0.post0"

[dev-packages]

[requires]
python_version = "3.7"

[pipenv]
allow_prereleases = true
a
hmmm, do you get the same error with
0.6.0
instead of
0.6.0.post0
d
yup
a
so we have
Copy code
# graphql-core pinned to range for Python 2 compataibility
graphql-core>=2.1,<3
and then something else must be adding all those other constraints
Could not find a version that matches graphql-core<3,<4,>=2.0<3,>=2.1,>=3.0.0a0
looks like
>=3.0.0a0
is the conflict
d
bizarre - I wonder where those constraints are coming from
a
searching github
loooooks like graphene
d
ah
a
python package management is truly the gift that keeps on giving
🙂 1
d
Lol
a
I'll consult the council of elders and get things fixed on our end - but in the mean time you could try to specify
graphene<3
(or something like that) in your pipfile and see if it works
🧙‍♂️ 2
d
yup sounds good. thanks @alex!
a
huh https://pypi.org/project/graphene/#history v3 is prerelease - does pipenv not respect prerelease flags?
i wonder if theres something else introducing the issue
d
it should! you can see in the Pipfile that there is an
allow_prereleases
config
i tried both with and without
a
huh is the error slightly different with it off?
d
oh wow ignore me! explicitly not allowing pre releases does fix this issue
🤦‍♂️
so we're good
a
noice