Skip to content

Consider merging config into mathesar package #2712

@apollo13

Description

@apollo13

Problem

Currently mathesar has a config package containing the settings and asgi/wsgi files. Since config is a rather generic name it could clash with other packages installed from pip. It would be preferred to have something like mathesar.wsgi & mathesar.settings.production to keep everything namespaced nicely. From a Django PoV this is doable and there would be no problems.

Proposed solution

Move config.settings/asgi/wsgi into mathesar package. Probably move config.urls to mathesar.root_urls & find a place for the context processors.

I realize this is backwards incompatible, but this would be a change that you really want to do now as opposed to sometime in the future when you already reached 1.0 or so… What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    affects: dxRelated to developer experiencefeedback: capturedFeedback in issue has been capturedreadyReady for implementationtype: enhancementuser reportedReported by a Mathesar userwork: backendRelated to Python, Django, and simple SQL

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions