Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fix DTC Studio shell compatibility with the community-base block check

Open
  • Is something wrong?
#435 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
django, python
Domain
backend, testing

Research direction

Reproduce the failure with uv run python manage.py check, then compare website.settings.local with website.settings.test and inspect the Studio adapter at templates/community_base/studio/base.html. Review the existing Studio shell work in #377 and determine whether the loader or block probe needs adjustment; done means local check and test commands pass while an incompatible shell is still rejected.

Written by the indexing model from the issue text.

Description

admin bug needs grooming P2

What happened?

When community-base v0.5.8 or later is linked into DTC and Django uses its default local settings, uv run python manage.py check reports community_base.studio.E001 for the site's Studio adapter. The same check passes under website.settings.test, which the maintained CI commands use. The problem is limited to local-settings behavior, but it prevents plain manage.py check and manage.py test commands from reaching their checks/tests.

Steps to reproduce

  1. In a DTC checkout, link or install community-base v0.5.8 or later.
  2. Run uv run python manage.py check (manage.py defaults to website.settings.local).
  3. Observe community_base.studio.E001 for community_base/studio/base.html.
  4. Compare with uv run python manage.py check --settings=website.settings.test, which passes with warnings only.

Expected behavior

The DTC Studio template chain is treated consistently across local and test settings. Resolve whether the local template loader should use the adapter at templates/community_base/studio/base.html or whether the block probe should account for its reachable nested blocks. Keep the check capable of rejecting a genuinely incompatible shell.

Context

The shared check first appears in community-base v0.5.8. The maintained package consumer CI and DTC course suite pass with test settings. Coordinate with the existing Studio shell work in #377 if it resolves the same template contract.

Dominant language
Python
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DataTalksClub/website

All issues in DataTalksClub/website

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.