Miserlou/Zappa

Warn Upon Packaging Namespace Collision

Open

#1127 opened on Sep 25, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (11,903 stars) (1,286 forks)batch import
enhancementhacktoberfesthelp wanted

Description

During packaging, Zappa may override packages if they have the same name - for instance with awesome-slugify and python-slugify, which both create slugify package directory.

Currently, Zappa fails silently. We should add a check and a warning during packaging.

Contributor guide

Tech stack
python
Domain
backenddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonZappa packaging basicsBasic understanding of Python packaging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Examine Zappa's packaging logic in the source code, likely in `handlers.py` or `core.py`. Look for how packages are collected and installed. Identify where duplicate package names could cause collisions and how to detect them. Implement a check that compares package names and emits a warning. See existing tests for packaging to understand expected behavior.