Package to Module Conversion

未关闭
#791 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 7 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
18/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
tooling

调研方向

The request is a package-to-module refactoring, the inverse of the existing topackage refactoring that the issue mentions; use that as the reference for how rope rewrites imports across a project. The issue leaves open how to merge __init__.py, bar.py and barbar.py into one file and how to rewrite from foo.bar import X references, so the design has to be settled before any code. Done would mean a tested refactoring that turns a package into a module and rewrites the imports, agreed with the maintainers first.

由索引模型根据 Issue 内容生成。

描述

I have multiple packages with containing very small modules (e.g. 10 lines of code).
I would like to turn a package into a module:

foo/
  __init__.py
 bar.py
 barbar.py

becomes: foo.py containing all code of foo/{__init__.py,bar.py, barbar.py} without relatives import. All other imports of a project needs to be rewritten, from foo.bar import X becomes from foo import X.

I see there is a topackage, so it would be kind of the inverse, I guess?

主要语言
Python
星标
2.2k
派生
197
平均合并
2 天 13 小时
30 天内合并 PR
5

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

python-rope/rope 的其他 Issue

查看 python-rope/rope 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。