Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
Keep a small explicit public API with clear module boundaries and type hints, follow semantic versioning, deprecate before removing with warnings and migration notes, and test against the supported Python and dependency versions in CI.
Everything importable tends to become public, so mark internals with leading underscores, define exports in init and all, and document what is supported. Ship type hints with a py.typed marker so consumers get static checking. Use semantic versioning: patch for fixes, minor for compatible features, major for breaking changes. Before removing something, emit DeprecationWarning for at least one minor release, provide a replacement and migration guide, and consider automated codemods for large migrations. Keep dependency ranges broad enough not to conflict with consumers' other packages, test a matrix of Python and dependency versions, and publish wheels to an internal package index. Tracking which services use which version helps plan the final removal.