For transparency, here's the plan to "migrate" the...
# development
b
For transparency, here's the plan to "migrate" the django dep inference code: • Instead of plugging into the new union (which I hope to remove), plugin into the normal dep inference union • To make it performant, only infer deps from files that "look" like migrations (under a "migrations" folder with a filename like ...) • Then do rudimentary AST traversal/scraping That will allow us to remove the existing dep inference union/code for Python wholesale in 2.18
h
I thought we would still need the existing dep inference code for Python 2.7?
b
Nope 🙂
❤️ 1
h
Oh right, because you switched to the PEG parser thing
noice!