Paul Ganssle - Why you shouldn't invoke setup.py directly
Why you shouldn't invoke setup.py directly TL;DR: The setuptools team no longer wants to be in the business of providing a command line interface and is actively working to become just a library for building packages. What you should do instead depends on your use case, but if you want some basic rules of thumb, there is a table in the summary section. This does not mean that setuptools itself is
Pythonã®ãƒ‘ッケージ管ç†ãƒ™ã‚¹ãƒˆãƒ—ラクティス - Qiita
※ãŠã™ã™ã‚ã®åŸºæº–ã«ã¯ä¸Šè¨˜ã€Œå°Žå…¥ã®æ‰‹è»½ã•ã€ã€Œå¦ç¿’ã®æ‰‹è»½ã•ã€ã€Œãƒ‘ッケージä¾å˜é–¢ä¿‚ã®è§£æ±ºã€ä»¥å¤–ã«ã€ã€Œå¯¾è±¡OSã¨ã®ç›¸æ€§ã€ã€Œæ¤œç´¢ã«ã‚ˆã‚‹æƒ…å ±ã®è¦‹ã¤ã‹ã‚Šã‚„ã™ã•ã€ã‚’考慮ã—ã¦ã„ã¾ã™ã€‚詳ã—ãã¯å¾Œè¿°ã—ã¾ã™ ç†è€…ã®ä¸»è¦³ãŒå…¥ã‚Šã¾ã™ãŒã€æ¦‚ã以下ã®ãƒ•ãƒãƒ¼ãƒãƒ£ãƒ¼ãƒˆã®ã‚ˆã†ã«é¸æŠžã™ã‚‹ã¨è‰¯ã„ã‹ã¨æ€ã„ã¾ã™ (詳ã—ãã¯å¾Œè¿°ã—ã¾ã™) ãªãŠã€å®Ÿç”¨ä¸Šãƒãƒžã‚Šã‚„ã™ã„プãƒã‚シ環境ã§ã®ä½¿ç”¨æ–¹æ³•ã«ã¤ã„ã¦ã‚‚ã€ä»¥ä¸‹ã®è¨˜äº‹ã«åˆ¥é€”ã¾ã¨ã‚ã¾ã—㟠必è¦çŸ¥è˜ ã“ã“ã‹ã‚‰å…ˆã¯ã€Pythonã®ãƒ‘ッケージ管ç†ãŒä½•ã‚’ã‚„ã£ã¦ã„ã‚‹ã‹ã‚’解説ã—ã¾ã™ã€‚ 「御託ã¯ã„ã„ã‹ã‚‰æ—©ã使ã„ãŸã„ï¼ã€ã¨ã„ã†æ–¹ã¯ã€ã€Œ3種類ã®æ–¹æ³•æ¯”較ã€ã®é …ç›®ã¾ã§é£›ã‚“ã§ãã ã•ã„ ã¾ãšã€ä¸€èˆ¬çš„ã«ã€Œãƒ‘ッケージ管ç†ã€ã¨å‘¼ã°ã‚Œã¦ã„ã‚‹è¦ç´ ã‚’ã€ä»¥ä¸‹ã®4ã¤ã®æ©Ÿèƒ½ã«åˆ†å‰²ã—ã¦è€ƒãˆã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ A. インタプリタ切替 (Pythonã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’切り替ãˆã‚‹) B. パッケージ切替 (パッケージã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’切り替ãˆã‚‹) C. パッ
ãã®Pythonパッケージ管ç†ã€venv + pipã§ã‚ˆããªã„ã§ã™ã‹? in 2023/1
ãã®Pythonパッケージ管ç†ã€venv + pipã§ã‚ˆããªã„ã§ã™ã‹? in 2023/1 å„所(主ã«Python界隈ã®å¤–)ã§ã€ŒPythonパッケージ管ç†ã©ã†ã™ã‚‹ã®ãŒæ£è§£ãªã®?ã€ã¨ã‚ˆã耳ã«ã™ã‚‹ã®ã§2023å¹´åˆé 時点ã§ã®ç§ã®è¦‹è§£ã‚’書ãã¾ã™ã€‚ tl;dr 多ãã®å ´åˆã®Pythonパッケージ管ç†ã¯venv(virtualenv) + pipã§æ¸ˆã‚€ã®ã§ã¯? å‰æ タイトルã«venvã¨ã¤ã„ã¦ã„ã¾ã™ãŒã€ä»¥é™venv(virtualenv)ã«ã¤ã„ã¦ã¯è¨€åŠã—ã¾ã›ã‚“。仮想環境内ã§ä½œæ¥ã—ã¦ã„ã‚‹å‰æã§è©±ã‚’進ã‚ã¾ã™ã€‚ ã“ã®è¨˜äº‹ã§ã¯åŸºæœ¬çš„ã«setup.py / setup.cfgã§ã¯ãªãpyproject.tomlã§ã®ãƒ‘ッケージ定義方法を採用ã—ã¾ã™ã€‚ã“ã‚Œã¯PEP 621ãŒã“ã“最近ã§æŽ¡æŠžãƒ»å®Ÿè£…ã•ã‚ŒãŸãŸã‚ã§ã™ã€‚ ãªãŠã€æƒ³å®šã—ã¦ã„ã‚‹Pythonã‚„å„ツールã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ä»¥ä¸‹ã®é€šã‚Šã§ã™ã€‚ Python >= 3.8 pip
Should Rye Exist? · astral-sh/rye · Discussion #6
This is how I feel about all the Python packaging. And this is why I never wanted to publish rye and kept it for myself. It's also incredibly hacky internally because it was never intended to be shared. However I really like what it does (at least in theory) and I desperately want it to exist. As it stands today, it solves my problems — sort of. I wish it solved more of my problems but to a large
pythonパッケージ管ç†ãƒ„ールryeを使ㆠ- 肉çƒã§ã‚ーボード
Pythonパッケージ管ç†ãƒ„ール ryeã®ä½¿ã„å‹æ‰‹ãŒã‚ˆã‹ã£ãŸã®ã§ä½¿ç”¨æ–¹æ³•ã‚’ã¾ã¨ã‚ã¾ã—ãŸã€‚ ryeã¨ã¯ GitHub: https://github.com/mitsuhiko/rye flaskã®ä½œè€…ã§ã‚ã‚‹ Armin Ronacheræ° (GitHubアカウント @mitsuhiko)ãŒå€‹äººåˆ©ç”¨ç›®çš„ã§ä½œæˆã—ãŸã€Pythonã®ãƒ‘ッケージ関係管ç†ãƒ„ールã§ã™ã€‚内部実装ã¯Rustã§ã™ã€‚ ryeãŒä½œæˆã•ã‚ŒãŸæ€æƒ³ãŒãƒªãƒã‚¸ãƒˆãƒª Should Rye Exist? ã®Discussionページã«æ›¸ã‹ã‚Œã¦ã„ã¾ã™ã€‚ Should Rye Exist?: XKCD #927 Disucssionä¸ã®å›³ã«ã‚るよã†ã«ã€å¾“æ¥ã®Pythonã®ãƒ‘ッケージ管ç†ã¯â€æ§˜ã€…ãªæ¨™æº–â€ãŒå˜åœ¨ã—ã€ã“ã®ã°ã‚‰ã¤ãを統一ã—よã†ã¨æ–°ã—ãパッケージ管ç†ãƒ„ールを導入ã—ã¦ã‚‚ã€â€æ–°ãŸãªæ¨™æº–ãŒè¿½åŠ ã•ã‚Œã‚‹ã ã‘â€ã¨ãªã‚Šã€çœŸã®ãƒ‘ッケージ管ç†ã®æ¨™æº–化を行ãˆã¦
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}