PEP 2: æ–°ã—ã„モジュールã®è¿½åŠ æ‰‹ç¶šã ==================================== 原文: http://www.python.org/dev/peps/pep-0002/ +---------------+----------------------------------------------+ | PEP | 2 | +---------------+----------------------------------------------+ | Title | Procedure for Adding New Modules | +---------------+----------------------------------------------+ | Version | 56077 | +---------------+----------------------------------------------+ | Last-Modified | 2007-06-22 20:50:54 +0200 (Fri, 22 Jun 2007) | +---------------+----------------------------------------------+ | Author | Martijn Faassen <faassen at infrae.com> | +---------------+----------------------------------------------+ | Status | Active | +---------------+----------------------------------------------+ | Type | Process | +---------------+----------------------------------------------+ | Created | 07-Jul-2001 | +---------------+----------------------------------------------+ | Post-History | 07-Jul-2001, 09-Mar-2002 | +---------------+----------------------------------------------+ イントãƒãƒ€ã‚¯ã‚·ãƒ§ãƒ³ -------------------- .. The Python Standard Library contributes significantly to Python's success. The language comes with "batteries included", so it is easy for people to become productive with just the standard library alone. It is therefore important that this library grows with the language, and that such growth is supported and encouraged. Python標準ライブラリã¯ã€Pythonã®æˆåŠŸã«å¤šå¤§ãªå¯„与をã—ã¾ã—ãŸã€‚"ãƒãƒƒãƒ†ãƒªãƒ¼ 内蔵"ã®è¨€èªžã¯ã€æ¨™æº–ライブラリã ã‘ã§äººã€…を生産的ã«ã—ã¾ã—ãŸã€‚ãã®ãŸã‚〠ã“ã®ãƒ©ã‚¤ãƒ–ラリãŒè¨€èªžã¨å…±ã«ç™ºå±•ã—ã€ãã—ã¦ã€ãã®ç™ºå±•ãŒåбã¿ã«ãªã‚‹ã“ã¨ãŒé‡ è¦ã¨ãªã‚‹ã®ã§ã™ã€‚ .. Many contributions to the library are not created by core developers but by people from the Python community who are experts in their particular field. Furthermore, community members are also the users of the standard library, applying it in a great diversity of settings. This makes the community well equipped to detect and report gaps in the library; things that are missing but should be added. ã“ã®ãƒ©ã‚¤ãƒ–ラリã¯ã€ä¸»è¦ãªé–‹ç™ºè€…ã ã‘ã§ãªãã€Pythonコミュニティã§ã®å„分野㧠ã®å°‚門家ã‹ã‚‰ã‚‚多大ãªå¯„与ã•らã«ã€ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ã®ãƒ¡ãƒ³ãƒãƒ¼ã¯ã“ã®æ¨™æº–ライブラ リã®ãƒ¦ãƒ¼ã‚¶ã§ã‚‚ã‚りã€å‰å¤§ãªã»ã©å¤šæ§˜ãªè¨å®šã‚’é©ç”¨ã—ã¦ãれã¾ã—ãŸã€‚ã“れã¯ã‚³ãƒŸãƒ¥ ニティã«ãƒ©ã‚¤ãƒ–ラリä¸ã®ãƒã‚°ã‚’発見ã—ã€å ±å‘Šã™ã‚‹èƒ½åŠ›ã‚’ã‚‚ãŸã‚‰ã—ã¦ã„ã¾ã™ã€‚失゠れãŸã‚‚ã®ã”ã¨ã¯ã€ä»˜ã‘åŠ ãˆã‚‰ã‚Œã‚‹ã®ã§ã™(訳注:定型å¥ï¼Ÿ)。 .. New functionality is commonly added to the library in the form of new modules. This PEP will describe the procedure for the _addition_ of new modules. PEP 4 deals with procedures for deprecation of modules; the _removal_ of old and unused modules from the standard library. Finally there is also the issue of _changing_ existing modules to make the picture of library evolution complete. PEP 3 and PEP 5 give some guidelines on this. The continued maintenance of existing modules is an integral part of the decision on whether to add a new module to the standard library. Therefore, this PEP also introduces concepts (integrators, maintainers) relevant to the maintenance issue. é€šå¸¸ã€æ–°ã—ã„æ©Ÿèƒ½ã¯æ–°ã—ã„モジュールã®å½¢ã¨ãªã£ã¦ãƒ©ã‚¤ãƒ–ラリã«ä»˜ã‘åŠ ãˆã‚‰ã‚Œã¾ ã™ã€‚ã“ã®PEPã¯ã€æ–°ã—ã„モジュールを **è¿½åŠ ** ã™ã‚‹æ‰‹ç¶šãã«ã¤ã„ã¦è¿°ã¹ã¦ã„ã¾ã™ã€‚ ã¾ãŸã€å¤ã„使ã‚れã¦ã„ãªã„モジュールを標準ライブラリã‹ã‚‰ **å–り除ã** 手続 ãã‚‚å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚最後ã«ã€ãƒ©ã‚¤ãƒ–ラリを完全ãªã‚‚ã®ã«ã™ã‚‹ãŸã‚ã«ã€æ—¢å˜ã®ãƒ¢ ジュールを **変更** ã™ã‚‹ã“ã¨ã«é–¢ã—ã¦ã‚‚è¿°ã¹ã‚‰ã‚Œã¦ã„ã¾ã™ã€‚PEP 3ã¨PEP 5ã¯ã“ ã®æ‰‹ç¶šãã«é–¢ã™ã‚‹ã‚¬ã‚¤ãƒ‰ãƒ©ã‚¤ãƒ³ã‚’æä¾›ã—ã¦ã„ã¾ã™ã€‚æ—¢å˜ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«å¯¾ã™ã‚‹ç¶™ ç¶šçš„ãªãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã¯ã€æ–°ã—ã„モジュールを付ã‘åŠ ãˆã‚‹æ±ºå®šã«é–¢ã‚らãšã€å®Œå…¨ãª ã‚‚ã®ã«ãªã‚‹ãŸã‚ã«å¿…è¦ãªéƒ¨åˆ†ã§ã™ã€‚ãã®ãŸã‚ã€ã“ã®PEPã¯ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã®å•題ã«é–¢ ã™ã‚‹é©åˆ‡ãªã‚³ãƒ³ã‚»ãƒ—ト(インテグレータã€ãƒ¡ãƒ³ãƒ†ãƒŠ)を紹介ã—ã¾ã™ã€‚ .. Integrators --------------- インテグレータ(訳注: é©åˆ‡ãªè¨³ã¯ãªã‚“ã ã‚ã†) ------------------------------------------ .. The integrators are a group of people with the following responsibilities: インテグレータã¯ä»¥ä¸‹ã®è²¬ä»»ã‚’æŒã¤äººã€…ã®é›†ã¾ã‚Šã§ã™ã€‚ .. - They determine if a proposed contribution should become part of the standard library. - ææ¡ˆãŒæ¨™æº–ライブラリã®ä¸€éƒ¨åˆ†ã«ãªã‚‹ã¹ãã‹ã‚’決定ã™ã‚‹ .. - They integrate accepted contributions into the standard library. - 標準ライブラリã¸ã®è²¢çŒ®ã‚’å—ç†ã™ã‚‹ .. - They produce standard library releases. - 標準ライブラリをリリースã™ã‚‹ .. This group of people shall be PythonLabs, led by Guido. - ã“ã®ã‚°ãƒ«ãƒ¼ãƒ—ã¯ã€Guidoã«ã‚ˆã£ã¦çއã„られã¦ã„ã‚‹PythonLabsã®äººã€…ã§ã‚ã‚‹ .. Maintainer(s) --------------- メンテナ --------------- .. All contributions to the standard library need one or more maintainers. This can be an individual, but it is frequently a group of people such as the XML-SIG. Groups may subdivide maintenance tasks among themselves. One ore more maintainers shall be the _head maintainer_ (usually this is also the main developer). Head maintainers are convenient people the integrators can address if they want to resolve specific issues, such as the ones detailed later in this document. 標準ライブラリã¸ã®å…¨ã¦ã®è²¢çŒ®ã¯ä¸€äººä»¥ä¸Šã®ãƒ¡ãƒ³ãƒ†ãƒŠã‚’å¿…è¦ã¨ã—ã¾ã™ã€‚ã“れ㯠XML-SIGã®ã‚ˆã†ãªç‹¬ç«‹ã—ãŸã€ã—ã‹ã—継続的ãªäººã€…ã®é›†ã¾ã‚Šã§ã™ã€‚グループã¯ãƒ¡ãƒ³ãƒ† ナンスã®ä»•事ã«å¿œã˜ã¦ç´°åˆ†åŒ–ã•れã¾ã™ã€‚一人以上ã®ãƒ¡ãƒ³ãƒ†ãƒŠãŒ **メンテナ長** (Head maintainer)ã¨ãªã‚Šã¾ã™(ã“ã®äººã¯å¤§ä½“ã®å ´åˆã«ãŠã„ã¦ã€ä¸»è¦é–‹ç™ºè€…ã§ã‚ã‚‹)。 メンテナ長ã¯ã€ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚¿ãŒã“ã®æ–‡æ›¸ã§å¾Œã«è¿°ã¹ã‚‹ã‚ˆã†ãªç‰¹å®šã®å•題を解決 ã—ã¦ã»ã—ã„ã¨æŒ‡ã—示ã—ã‚„ã™ã„人々ã§ã™ã€‚ .. Developers(s) --------------- 開発者 --------------- .. Contributions to the standard library have been developed by one or more developers. The initial maintainers are the original developers unless there are special circumstances (which should be detailed in the PEP proposing the contribution). 標準ライブラリã¸ã®è²¢çŒ®ã¯ã€ä¸€äººä»¥ä¸Šã®é–‹ç™ºè€…ã«ã‚ˆã£ã¦é–‹ç™ºã•れã¾ã™ã€‚(PEPã®è²¢çŒ® ã¸ã®èª˜ã„ã«ã¦è¿°ã¹ã‚‰ã‚Œã‚‹ã‚ˆã†ãª)特別ãªäº‹æƒ…ãŒãªã„é™ã‚Šã€æœ€åˆã®ãƒ¡ãƒ³ãƒ†ãƒŠã¯å…ƒã€…㮠開発者ã§ã™ã€‚ .. Acceptance Procedure å—ç†ã®æ‰‹ç¶šã --------------- .. When developers wish to have a contribution accepted into the standard library, they will first form a group of maintainers (normally initially consisting of themselves). 開発者ãŒè²¢çŒ®ã‚’標準ライブラリã«å—ã‘å…¥ã‚Œã¦æ¬²ã—ã„ã¨é¡˜ã£ãŸã¨ãã€æœ€åˆã«ãƒ¡ãƒ³ãƒ† ナã®ã‚°ãƒ«ãƒ¼ãƒ—を作ã£ã¦ãã ã•ã„(通常最åˆã¯å½¼ã‚‰è‡ªèº«ã§æ§‹æˆã•れã¾ã™)。 .. Then, this group shall produce a PEP called a library PEP. A library PEP is a special form of standards track PEP. The library PEP gives an overview of the proposed contribution, along with the proposed contribution as the reference implementation. This PEP should also contain a motivation on why this contribution should be part of the standard library. ãれã‹ã‚‰ã€ãã®ã‚°ãƒ«ãƒ¼ãƒ—ã¯ãƒ©ã‚¤ãƒ–ラリPEPã¨å‘¼ã°ã‚Œã‚‹PEPã®æ‰‹ç¶šãを進ã‚ã¾ã™ã€‚ラ イブラリPEPã¯ã‚¹ã‚¿ãƒ³ãƒ€ãƒ¼ãƒ‰ãƒˆãƒ©ãƒƒã‚¯ã®PEPã®ã†ã¡ã®ç‰¹åˆ¥ãªPEPã§ã™ã€‚ã“ã®ãƒ©ã‚¤ãƒ–ラ リPEPã¯ææ¡ˆã•れãŸè²¢çŒ®ã®æ¦‚è¦ã¨ã€å‚照実装をæä¾›ã™ã‚‹ã“ã¨ã«ãªã‚Šã¾ã™ã€‚ã“ã®PEP ã¯ãªãœã“ã®è²¢çŒ®ãŒæ¨™æº–ライブラリã®ä¸€éƒ¨ã¨ãªã‚‰ãªã‘れã°ãªã‚‰ãªã„ã®ã‹ã¨ã„ã†ç†ç”± ã‚’å«ã‚€å¿…è¦ãŒã‚りã¾ã™ã€‚ .. One or more maintainers shall step forward as PEP champion (the people listed in the Author field are the champions). The PEP champion(s) shall be the initial head maintainer(s). 一人以上ã®ãƒ¡ãƒ³ãƒ†ãƒŠãŒPEPãƒãƒ£ãƒ³ãƒ”オン(è‘—è€…ã«æŒ™ãŒã£ã¦ã„る人々ãŒãƒãƒ£ãƒ³ãƒ”オン ã§ã™)ã¨ã—ã¦ã€æ‰‹ç¶šãを進ã‚ã‚‹å¿…è¦ãŒã‚りã¾ã™ã€‚ã“ã®PEPãƒãƒ£ãƒ³ãƒ”オン(é”)ãŒã€æœ€ åˆã®ãƒ¡ãƒ³ãƒ†ãƒŠé•·ã§ã™ã€‚ .. As described in PEP 1, a standards track PEP should consist of a design document and a reference implementation. The library PEP differs from a normal standard track PEP in that the reference implementation should in this case always already have been written before the PEP is to be reviewed for inclusion by the integrators and to be commented upon by the community; the reference implementation _is_ the proposed contribution. PEP 1ã§è¿°ã¹ã‚‰ã‚ŒãŸé€šã‚Šã€ã‚¹ã‚¿ãƒ³ãƒ€ãƒ¼ãƒ‰ãƒˆãƒ©ãƒƒã‚¯PEPã¯è¨è¨ˆã¨å‚照実装をå«ã¾ãªã‘ れã°ãªã‚Šã¾ã›ã‚“。ライブラリPEPã¯é€šå¸¸ã®ã‚¹ã‚¿ãƒ³ãƒ€ãƒ¼ãƒ‰ãƒˆãƒ©ãƒƒã‚¯PEPã¨ç•°ãªã‚Šã€ 常ã«PEPãŒæ›¸ã‹ã‚Œã‚‹ã‚ˆã‚Šå‰ã«å‚照実装ãŒãªãã¦ã¯ãªã‚Šã¾ã›ã‚“。ã¾ãŸã€ã“ã®å‚照実装 ã¯ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚¿ã«ã‚ˆã£ã¦ãƒ¬ãƒ“ューã•れã€ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ã‹ã‚‰ã‚³ãƒ¡ãƒ³ãƒˆã‚’å—ã‘付㑠ãªãã¦ã¯ãªã‚Šã¾ã›ã‚“。å‚照実装 **ã“ããŒ** ææ¡ˆã•れã¦ã„る貢献ãªã®ã§ã™ã€‚ .. This different requirement exists for the following reasons: ã“ã®ç•°ãªã‚‹è¦æ±‚äº‹é …ã¯ã€ä»¥ä¸‹ã®ç†ç”±ã«ã‚ˆã£ã¦æ±‚ã‚られã¦ã„ã¾ã™ã€‚ .. - The integrators can only properly evaluate a contribution to the standard library when there is source code and documentation to look at; i.e. the reference implementation is always necessary to aid people in studying the PEP. ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã¨æ–‡ç« を調ã¹ã‚‹ã¨ãã«ã€ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚¿ã“ããŒæ¨™æº–ライブラリã¸ã® 貢献をæ£ã—ã判æ–ã§ãã‚‹ã‹ã‚‰ã§ã™ã€‚ã™ãªã‚ã¡ã€å‚照実装ã¯PEPを勉強ã—ã¦ã„る人々 ã«å–ã£ã¦å¸¸ã«å¿…è¦ãªã®ã§ã™ã€‚(訳注: 自信無) .. - Even rejected contributions will be useful outside the standard library, so there will a lower risk of waste of effort by the developers. è²¢çŒ®ãŒæ‹’å¦ã•れãŸã¨ã—ã¦ã‚‚ã€æ¨™æº–ライブラリ以外ã«ã¨ã£ã¦ã¯æœ‰ç›Šãªå ´åˆãŒã‚り㾠ã™ã€‚ãã®ãŸã‚ã€é–‹ç™ºè€…ã®åŠªåŠ›ã‚’ç„¡é§„ã«ã™ã‚‹ãƒªã‚¹ã‚¯ã‚’低ãã—ã¾ã™ã€‚ .. - It will impress the integrators of the seriousness of contribution and will help guard them against having to evaluate too many frivolous proposals. インテグレータã®çœŸå‰£ãªè²¢çŒ®ãŒè‰¯ã„å°è±¡ã‚’与ãˆã€ä¸çœŸé¢ç›®ãªææ¡ˆã‚’æ•°å¤šãæ¤œè¨Žã— ãªã‘れã°ãªã‚‰ãªã„事態を防ãŽã¾ã™ã€‚ .. Once the library PEP has been submitted for review, the integrators will then evaluate it. The PEP will follow the normal PEP work flow as described in PEP 1. If the PEP is accepted, they will work through the head maintainers to make the contribution ready for integration. 一度ライブラリPEPãŒãƒ¬ãƒ“ューã«ç”³è«‹ã•れるã¨ã€ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚¿ã¯ãれを評価ã—ã¾ ã™ã€‚PEPã¯PEP 1ã§è¿°ã¹ã‚‰ã‚ŒãŸæ¨™æº–PEPã®ãƒ¯ãƒ¼ã‚¯ãƒ•ãƒãƒ¼ã«å‰‡ã‚Šã¾ã™ã€‚ã‚‚ã—ãã®PEP㌠å—ç†ã•れãŸå ´åˆã€ãƒ¡ãƒ³ãƒ†ãƒŠé•·ã«å›žè¦§ã•れã€ãã®è²¢çŒ®ã‚’標準ライブラリã«çµ±åˆã™ã‚‹ 準備ã«ã¨ã‚Šã‹ã‹ã‚Šã¾ã™ã€‚ .. Maintenance Procedure ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã®æ‰‹ç¶šã -------------------- .. After a contribution has been accepted, the job is not over for both integrators and maintainers. The integrators will forward any bug reports in the standard library to the appropriate head maintainers. 貢献ãŒå—ç†ã•れれã°ã€ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚¿ã¨ãƒ¡ãƒ³ãƒ†ãƒŠã®ä¸¡æ–¹ã«ã¨ã£ã¦ãã®ä»•事ãŒçµ‚゠りã€ã¨ã„ã†ã‚ã‘ã§ã¯ã‚りã¾ã›ã‚“。インテグレータã¯ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚¿ã¯æ¨™æº–ライブ ラリä¸ã®ã©ã‚“ãªãƒã‚°å ±å‘Šã‚‚ã€é©åˆ‡ãªãƒ¡ãƒ³ãƒ†ãƒŠé•·ã«è»¢é€ã—ã¾ã™ã€‚ .. Before the feature freeze preparing for a release of the standard library, the integrators will check with the head maintainers for all contributions, to see if there are any updates to be included in the next release. The integrators will evaluate any such updates for issues like backwards compatibility and may require PEPs if the changes are deemed to be large. 標準ライブラリã®ãƒªãƒªãƒ¼ã‚¹ã«å‚™ãˆã¦æ©Ÿèƒ½ã‚’å‡çµã™ã‚‹æº–備をã™ã‚‹å‰ã«ã€ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ ã‚¿ã¯ãƒ¡ãƒ³ãƒ†ãƒŠé•·ã¨ä¸€ç·’ã«ã€æ¬¡ã®ãƒªãƒªãƒ¼ã‚¹ã«å«ã‚€æ›´æ–°ãŒãªã„ã‹å…¨ã¦ã®è²¢çŒ®ã‚’ãƒã‚§ãƒƒ クã—ã¾ã™ã€‚インテグレータã¯ãã®æ›´æ–°ã‚’ã€å¾Œæ–¹äº’æ›æ€§ãŒä¿ãŸã‚Œã¦ã‚‹ã‹ãªã©ã‚’評価 ã—ã¾ã™ã€‚ã¾ãŸã€æ›´æ–°ãŒå¤§ãã™ãŽã‚‹å ´åˆã¯PEPãŒå¿…è¦ã¨ãªã‚‹å ´åˆã‚‚ã‚りã¾ã™ .. The head maintainers should take an active role in keeping up to date with the Python development process. If a head maintainer is unable to function in this way, he or she should announce the intention to step down to the integrators and the rest of the maintainers, so that a replacement can step forward. The integrators should at all times be capable of reaching the head maintainers by email. メンテナ長ã¯Pythonã®é–‹ç™ºãƒ—ãƒã‚»ã‚¹ã‚’最新ã«ä¿ã¤ãŸã‚ã«æ´»ç™ºãªå½¹ç›®ã‚’æ‹…ã†å¿…è¦ãŒ ã‚りã¾ã™ã€‚ã‚‚ã—メンテナ長ãŒãã®å½¹ç›®ã‚’ã§ããªã„ã°ã‚ã„ã€ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚¿ã«é™æ ¼ ã™ã‚‹ã¨ã„ã†ã‚¢ãƒŠã‚¦ãƒ³ã‚¹ã‚’ã™ã‚‹å¿…è¦ãŒã‚りã¾ã™ã€‚ã“れã«ã‚ˆã‚Šã€ãƒ¡ãƒ³ãƒ†ãƒŠã®æ®‹ã‚Šã®äºº ãŒæ˜‡æ ¼ã™ã‚‹ã“ã¨ã«ãªã‚Šã¾ã™ã€‚インテグレータã¯ãƒ¡ãƒ³ãƒ†ãƒŠé•·ã¨E-メールã§é€£çµ¡ã‚’å– ã‚Šåˆãˆã‚‹ã‚ˆã†ã«ã—ã¦ãŠãå¿…è¦ãŒã‚りã¾ã™ã€‚ .. In the case where no head maintainer can be found (possibly because there are no maintainers left), the integrators will issue a call to the community at large asking for new maintainers to step forward. If no one does, the integrators can decide to declare the contribution deprecated as described in PEP 4. (ã‚‚ã†ãƒ¡ãƒ³ãƒ†ãƒŠãŒã„ãªã„ãªã©ã«ã‚ˆã£ã¦)メンテナ長ãŒè¦‹ã¤ã‹ã‚‰ãªã„å ´åˆã¯ã€ã‚¤ãƒ³ãƒ† ã‚°ãƒ¬ãƒ¼ã‚¿ã¯æ˜‡æ ¼ã™ã‚‹ãŸã‚ã®æ–°ã—ã„メンテナをコミュニティã‹ã‚‰åºƒã募集ã—ã¾ã™ã€‚ ã‚‚ã—も誰もã„ãªã„å ´åˆã€ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚¿ã¯PEP 4ã§è¿°ã¹ã‚‰ã‚Œã¦ã„るよã†ã«ã€ã㮠貢献を廃æ¢å®£è¨€ã™ã‚‹å¯èƒ½æ€§ãŒã‚りã¾ã™ã€‚ .. Open Issues ------------- 未解決ãªå•題 ------------- .. There needs to be some procedure so that the integrators can always reach the maintainers (or at least the head maintainers). This could be accomplished by a mailing list to which all head maintainers should be subscribed (this could be python-dev). Another possibility, which may be useful in any case, is the maintenance of a list similar to that of the list of PEPs which lists all the contributions and their head maintainers with contact info. This could in fact be part of the list of the PEPs, as a new contribution requires a PEP. But since the authors/owners of a PEP introducing a new module may eventually be different from those who maintain it, this wouldn't resolve all issues yet. インテグレータã¯ãƒ¡ãƒ³ãƒ†ãƒŠ(最低é™ãƒ¡ãƒ³ãƒ†ãƒŠé•·ã¨)ã¨å¸¸ã«é€£çµ¡ã‚’ã¨ã‚Œã‚‹ã‚ˆã†ãªæ–¹æ³• ãŒå¿…è¦ã§ã™ã€‚ãã®ãŸã‚ã«ã¯ã€å…¨ã¦ã®ãƒ¡ãƒ³ãƒ†ãƒŠé•·ãŒãƒ¡ãƒ¼ãƒªãƒ³ã‚°ãƒªã‚¹ãƒˆ(python-dev㌠é©å½“ã‹)ã‚’è³¼èªã™ã‚‹ã“ã¨ãªã©ãŒæ–¹æ³•ã¨ã—ã¦æŒ™ã’られã¾ã™ã€‚ä»–ã®å¯èƒ½æ€§ã¨ã—ã¦ã¯ã€ PEPリストã¨åŒã˜ã‚ˆã†ãªãƒªã‚¹ãƒˆã‚’å…¨ã¦ã®è²¢çŒ®ã«ã¤ã„ã¦ä½œæˆã—ã€ãれã«ãƒ¡ãƒ³ãƒ†ãƒŠé•·ã® 連絡先も併記ã—ã¦ãŠãã®ã§ã™ã€‚PEPã‚’è¦æ±‚ã™ã‚‹æ–°ã—ã„貢献ã«ã¯ã€PEPリストã®ä¸€éƒ¨ ã¨ã—ã¦å®Ÿéš›ãªã£ã¦ã„ã¾ã™(訳注: 自信無)。ã—ã‹ã—ã€æ–°ã—ã„モジュールを導入ã—㟠PEPã®è‘—者ã¨ç®¡ç†è€…ã¨ãŒåˆ¥ã«ãªã‚‹äº‹æ…‹ãŒèµ·ãã¦ã—ã¾ã„ã¾ã™ã€‚ .. This relates to all the technical issues; check-in privileges, coding style requirements, documentation requirements, test suite requirements. These are preferably part of another PEP. ã“ã®ä»¶ã¯ã€å…¨ã¦ã®æŠ€è¡“çš„ãªå•題ã«é–¢é€£ã—ã¾ã™ã€‚ãƒã‚§ãƒƒã‚¯ã‚¤ãƒ³æ¨©é™ã€ã‚³ãƒ¼ãƒ‡ã‚£ãƒ³ã‚° スタイルã®è¦æ±‚ã€æ–‡æ›¸åŒ–ã®è¦æ±‚ã€ãƒ†ã‚¹ãƒˆã®è¦æ±‚。ã“れã«é–¢ã—ã¦ã¯åˆ¥ã®PEPã§è¿°ã¹ã‚‹ æ–¹ãŒè‰¯ã„ã§ã—ょã†ã€‚ .. Should the current standard library be subdivided among maintainers? Many parts already have (informal) maintainers; it may be good to make this more explicit. ç¾åœ¨ã®æ¨™æº–ライブラリã¯ãƒ¡ãƒ³ãƒ†ãƒŠã®é–“ã§ç´°åˆ†åŒ–ã•れるã¹ãã‹ï¼Ÿå¤šãã®éƒ¨åˆ†ã«ã¯ã™ ã§ã«(éžå…¬å¼ã®)メンテナãŒã„ã¾ã™ã€‚ã‚‚ã£ã¨æ˜Žæ–‡åŒ–ã•ã›ã‚‹ã“ã¨ãŒã„ã„考ãˆã‹ã‚‚ã—れ ã¾ã›ã‚“。 .. Perhaps there is a better word for 'contribution'; the word 'contribution' may not imply enough that the process (of development and maintenance) does not stop after the contribution is accepted and integrated into the library. '貢献(contribution)'よりもã£ã¨ã„ã„å˜èªžãŒã‚ã‚‹ã‹ã‚‚ã—れã¾ã›ã‚“。'貢献'ã¨ã„ㆠ言葉ã¯ãƒ©ã‚¤ãƒ–ラリã«çµ±åˆã•れãŸã‚ã¨ã‚‚貢献をæ¢ã‚ãªã„ã¨ã„ã†ãã®(開発や管ç†ã®)プãƒã‚»ã‚¹ã‚’ååˆ†ã«æ„味ã—ã¦ã„ãªã„ã‹ã‚‚ã—れã¾ã›ã‚“。 .. Relationship to the mythical Catalog? 関連性ã¨ã¯ç¥žè©±ã®ã‚«ã‚¿ãƒã‚°ã‹ï¼Ÿ(訳注: æ„味ãŒã¨ã‚Œãªã„) .. Copyright --------------- 著作権 --------------- .. This document has been placed in the public domain. ã“ã®ãƒ‰ã‚ュメントã¯ãƒ‘ブリック・ドメインã«å±žã—ã¾ã™ã€‚ Local Variables: coding: utf-8 End: