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
The notion of PROJECT_PATH was tied to the old one-dimensional single-dir-based distribution where the kalite package was in limbo between being a django app and a django project.
It didn't really make itself understandable, neither, because the project was either the top-most level / or the /kalite/ dir.
Everywhere that PROJECT_PATH is used, it reveals some level of implicit structure. We need to go through all the occurrences and replace them with the new settings strategy #4054
On a secondary note, PROJECT_PATH was actually never a "setting", it was never supposed to be changed.
The notion of
PROJECT_PATH
was tied to the old one-dimensional single-dir-based distribution where thekalite
package was in limbo between being a django app and a django project.It didn't really make itself understandable, neither, because the project was either the top-most level
/
or the/kalite/
dir.Everywhere that
PROJECT_PATH
is used, it reveals some level of implicit structure. We need to go through all the occurrences and replace them with the new settings strategy #4054On a secondary note, PROJECT_PATH was actually never a "setting", it was never supposed to be changed.
The text was updated successfully, but these errors were encountered: