You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can't import the bootstrapped Literary in the same namespace as the Literary development environment, because both resolve imports against literary.
The easiest solution here is to rename the source package name src/literary_source to the canonical name at build time. The challenge will be in doing this cleanly; it's more of a Hatch thing than something Literary needs to know about.
The above solution wouldn't work with any scripts that reference literary; they'd use the bootstrapping version. That's probably what we want.
The text was updated successfully, but these errors were encountered:
We can't import the bootstrapped Literary in the same namespace as the Literary development environment, because both resolve imports against
literary
.The easiest solution here is to rename the source package name
src/literary_source
to the canonical name at build time. The challenge will be in doing this cleanly; it's more of a Hatch thing than something Literary needs to know about.The above solution wouldn't work with any scripts that reference
literary
; they'd use the bootstrapping version. That's probably what we want.The text was updated successfully, but these errors were encountered: