Re: [Python-Dev] Packaging in Python 2 anyone ?
On 15 August 2011 11:31, Tarek Ziadé wrote: > IOW, the task to do is: > > 1/ copy packaging and all its stdlib dependencies in a standalone project > 2/ rename packaging to distutils2 > 3/ make it work under older 2.x and 3.x (2.x would be the priority) < > 4/ release it, promote its usage > 5/ consolidate the API with the feedback received One thing that I, as a semi-interested bystander, would like to see is sort of a component of 4. Namely, a document somewhere addressing the question of why I, as a current user of distutils (setup.py, etc), should convert my project to use packaging/distutils2 - and what I'd need to do so. At the moment, I see no benefit to me in migrating. New projects, or projects that already know that they want one or more of the benefits that packaging/distutils2/setuptools bring, are a different matter. It's projects with needs satisfied by distutils, and code invested a distutils-based solution, that could do with some persuasion. I checked the docs, and "Distributing Python Modules" is for new projects, and "What's new" basically says "we expect you to migrate" but has no reasons or guidelines. If someone borrows the time machine and makes this already available, so much the better. Pointers would be appreciated! Paul. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Packaging in Python 2 anyone ?
> One thing that I, as a semi-interested bystander, would like to see is > sort of a component of 4. Namely, a document somewhere addressing the > question of why I, as a current user of distutils (setup.py, etc), > should convert my project to use packaging/distutils2 - and what I'd > need to do so. I’m working on such a document, first in a doc set outside of the Python docs, and when it’s ready as an official HOWTO. (I’ll send the URL when I finish and publish it.) > I checked the docs, and "Distributing Python Modules" is for new > projects, That doc set is for distutils, unless you meant “Distributing Python Projects”, which is currently under severe updating. Regards ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Packaging in Python 2 anyone ?
On 19 August 2011 16:40, Éric Araujo wrote: >> One thing that I, as a semi-interested bystander, would like to see is >> sort of a component of 4. Namely, a document somewhere addressing the >> question of why I, as a current user of distutils (setup.py, etc), >> should convert my project to use packaging/distutils2 - and what I'd >> need to do so. > > I’m working on such a document, first in a doc set outside of the Python > docs, and when it’s ready as an official HOWTO. (I’ll send the URL when > I finish and publish it.) Nice :-) I'll try to provide some feedback when it's ready. >> I checked the docs, and "Distributing Python Modules" is for new >> projects, > > That doc set is for distutils, unless you meant “Distributing Python > Projects”, which is currently under severe updating. Sorry, I did indeed mean "... Projects" - I had looked at the Python 3.3 doc tree, and hadn't noticed that the name had changed. Paul. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2011-08-12 - 2011-08-19)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open2937 (+14)
closed 21630 (+28)
total 24567 (+42)
Open issues with patches: 1266
Issues opened (31)
==
#12409: Moving "Documenting Python" to Devguide
http://bugs.python.org/issue12409 reopened by eric.araujo
#12745: Python2 or Python3 page
http://bugs.python.org/issue12745 opened by JBernardo
#12746: normalization is affected by unicode width
http://bugs.python.org/issue12746 opened by benjamin.peterson
#12749: lib re cannot match non-BMP ranges (all versions, all builds)
http://bugs.python.org/issue12749 opened by tchrist
#12750: datetime.strftime('%s') should respect tzinfo
http://bugs.python.org/issue12750 opened by Daniel.O'Connor
#12753: \N{...} neglects formal aliases and named sequences from Unico
http://bugs.python.org/issue12753 opened by tchrist
#12754: Add alternative random number generators
http://bugs.python.org/issue12754 opened by rhettinger
#12757: undefined name in doctest.py
http://bugs.python.org/issue12757 opened by georg.brandl
#12758: time.time() returns local time instead of UTC
http://bugs.python.org/issue12758 opened by maksbotan
#12759: "(?P=)" input for Tools/scripts/redemo.py throw an exception
http://bugs.python.org/issue12759 opened by fredeom
#12760: Add create mode to open()
http://bugs.python.org/issue12760 opened by David.Townshend
#12761: Typo in Doc/license.rst
http://bugs.python.org/issue12761 opened by jwilk
#12762: EnvironmentError_str contributes to unportable code
http://bugs.python.org/issue12762 opened by jwilk
#12764: segfault in ctypes.Struct with bad _fields_
http://bugs.python.org/issue12764 opened by amaury.forgeotdarc
#12765: test_packaging failure under Snow Leopard
http://bugs.python.org/issue12765 opened by pitrou
#12767: document threading.Condition.notify
http://bugs.python.org/issue12767 opened by eli.bendersky
#12768: docstrings for the threading module
http://bugs.python.org/issue12768 opened by eli.bendersky
#12769: String with NUL characters truncated by ctypes when assigning
http://bugs.python.org/issue12769 opened by Rafal.Dowgird
#12771: 2to3 -d adds extra whitespace
http://bugs.python.org/issue12771 opened by VPeric
#12772: fractional day attribute in datetime class
http://bugs.python.org/issue12772 opened by Miguel.de.Val.Borro
#12774: Warning -- multiprocessing.process._dangling was modified by t
http://bugs.python.org/issue12774 opened by ned.deily
#12775: immense performance problems related to the garbage collector
http://bugs.python.org/issue12775 opened by dsvensson
#12776: argparse: type conversion function should be called only once
http://bugs.python.org/issue12776 opened by arnau
#12777: Inconsistent use of VOLUME_NAME_* with GetFinalPathNameByHandl
http://bugs.python.org/issue12777 opened by pitrou
#12778: JSON-serializing a large container takes too much memory
http://bugs.python.org/issue12778 opened by pitrou
#12779: Update packaging documentation
http://bugs.python.org/issue12779 opened by eric.araujo
#12780: Clean up tests for pyc/pyo in __file__
http://bugs.python.org/issue12780 opened by eric.araujo
#12781: Mention SO_REUSEADDR near socket doc examples
http://bugs.python.org/issue12781 opened by sandro.tosi
#12782: Multiple context expressions do not support parentheses for co
http://bugs.python.org/issue12782 opened by Julian
#12783: test_posix failure on FreeBSD 6.4: test_get_and_set_scheduler_
http://bugs.python.org/issue12783 opened by neologix
#12785: list_distinfo_file is wrong
http://bugs.python.org/issue12785 opened by eric.araujo
Most recent 15 issues with no replies (15)
==
#12785: list_distinfo_file is wrong
http://bugs.python.org/issue12785
#12783: test_posix failure on FreeBSD 6.4: test_get_and_set_scheduler_
http://bugs.python.org/issue12783
#12782: Multiple context expressions do not support parentheses for co
http://bugs.python.org/issue12782
#12776: argparse: type conversion function should be called only once
http://bugs.python.org/issue12776
#12772: fractional day attribute in datetime class
http://bugs.python.org/issue12772
#12771: 2to3 -d adds extra whitespace
http://bugs.python.org/issue12771
#12768: docstrings for the threading module
http://bugs.python.org/issue12768
#12759: "(?P=)" input for Tools/scripts/redemo.py throw an exception
http://bugs.python.org/issue12759
#12742: Add support for CESU-8 encoding
http://bugs.python.org/issue12742
#12739: read stuck with multithreading and simultaneous subprocess.Pop
http://bugs.python.org/issue12739
#12736: Request for python casemapping functions to use full not simpl
http://bugs.python.org/issue12736
#12735: request full Unicode collation support in std python library
http://bugs.python.org
Re: [Python-Dev] cpython (3.2): NUL -> NULL
On 18Aug2011 20:51, Stefan Krah wrote: | Antoine Pitrou wrote: | > On Thu, 18 Aug 2011 17:49:28 +0200 | > benjamin.peterson wrote: | > > -PyErr_SetString(PyExc_TypeError, "embedded NUL character"); | > > +PyErr_SetString(PyExc_TypeError, "embedded NULL character"); | > | > Are you sure? IIRC, NUL is the little name of ASCII character 0 | > (while NULL would be the NULL pointer). | | Yes, that's the traditional name. I was surprised that the C99 standard uses | "null character" in almost all cases. Example: | | "The construction '\0' is commonly used to represent the null character." | | So I think it should be either NUL or "null character" with the lower | case spelling. +1 from me, too. -- Cameron Simpson DoD#743 http://www.cskk.ezoshosting.com/cs/ I like to keep an open mind, but not so open my brains fall out. - New York Times Chairman Arthur Sulzberger ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
