meaning you can put a git uri and hash in requirements.txt

one sec

the pypi upload is definitely messed up

yeah, so this works fine pip installing from source

<git+ssh://git@github.com/dagster-io/dagster.git@0.2.8.post1#egg=dagster&subdirectory=python_modules/dagster>

my bet is on something like stray .pyc file

yeah or dist/ from some other build

so i think we need to add into the release process a step to clone the repo fresh

that's good hygiene anyway

honestly i think i could simplify the release tools quite a bit by having them do that, though the quick fix is just change process

yeah the clean repo thing sounds goodd

good

so the immediate fix is: install from

<git+ssh://git@github.com/dagster-io/dagster.git@0.2.8.post1#egg=dagster&subdirectory=python_modules/dagster>

@schrockn do you want to release 0.2.8.post2 or shall i?

i’m almost done

i can do it

do you want to do the clean repo thing and then use it to push 0.3.4?

this is such a throwback to be on this branch

only 10 ci/cd jobs

so quaint!

i still want to know what this pypi propagation delay is

yes, i'll do the clean repo thing for 0.3.4 -- probably won't rewrite the tooling this afternoon but i'll put up a tracking task

cool

it might be something else

i deleted all the pyc files

and it didn’t resolve it

i’ll do a clean repo as well

for my edification, can i see

tree

on your dagster repo directory

what do you mean by tree

like run

tree dagster