Mailman 3 March 2008 - Python-Dev

Proposal: from __future__ import unicode_string_literals
by Lennart Regebro March 25, 2008

March 25, 2008

Eric Smith wrote: > It's not implementable because the work has to occur in ast.c (see > Py_UnicodeFlag). It can't occur later, because you need to skip the > encoding being done in parsestr(). But the __future__ import can only > be interpreted after the AST is built, at which time the encoding has > already been applied. There are some radical things you could do to > work around this, but it would be a gigantic change. Oh, <swear words>! > Pretty much. And … [View More]

10 29

Re: [Python-Dev] [Python-checkins] r61709 - python/trunk/Doc/library/functions.rst python/trunk/Doc/library/future_builtins.rst python/trunk/Doc/library/python.rst
by Jim Jewett March 25, 2008

March 25, 2008

What is the precise specification of the builtin "print" function. Does it call "str", or does it just behave as if the builtin str had been called? In 2.5, the print statement ignores any overrides of the str builtin, but I'm not sure whether a _function_ should -- and I do think it should be specified. -jJ On 3/21/08, georg.brandl <python-checkins(a)python.org> wrote: > New Revision: 61709 ============================================================================== > +++ … [View More]

2 1

Proposal: from __future__ import unicode_string_literals
by Jim Jewett March 24, 2008

March 24, 2008

> Maybe it's not apparent to people that hasn't > developed in that kind of environment, and > I'm sorry I'm not able to make this clearer. I think I understand the issue. Some contributors will be running under 2.6, others will be running under 3.0. Either the code forks, or one of them is working with (and developing patches against) the result of a compilation step, instead of against the original source code. For example, if I'm using the (real source) py2.6 code, and I create … [View More]

3 2

windows standard [was: PEP 365 (Adding the pkg_resources module)]
by Jim Jewett March 24, 2008

March 24, 2008

Terry Reedy > The standard (and to me, preferable) way of dealing > with such things is to have an 'installation manager' > that can reinstall as well as delete and that has a > check box for various things to delete. This is what > Python needs. Paul Moore: > I'd dispute strongly that this is a "standard". > It may be preferable, but I'm not sure where you > see evidence of it being a standard. When I install a large program (such as developer tools, or python … [View More]

3 2

PEP 3127 (Integer Literal Support and Syntax): %o and %b
by Eric Smith March 24, 2008

March 24, 2008

I've been double checking the PEP 3127 implementation in py3k and the backport I did to 2.6. The PEP says this about the % operator: "The string (and unicode in 2.6) % operator will have 'b' format specifier added for binary, and the alternate syntax of the 'o' option will need to be updated to add '0o' in front, instead of '0'." The %b operator was not added to 3.0, so I'll look into doing that in both 2.6 and 3.0 (which I opened as issue 2416). What should be done for '%#o' formatting … [View More]

2 2

Making sys.py3k_warning writable
by Steven Bethard March 23, 2008

March 23, 2008

Right now, test_py3kwarn only runs if the test suite is run using the -3 command line flag to Python. So for most regrtest runs (e.g. the buildbots) this test will never be run. It would be nice to be able to turn the flag on from Python (e.g. within test_py3kwarn). Is that possible? Here's what I tried and it didn't seem to work:: $ python_d.exe Python 2.6a1+ (trunk:61715M, Mar 21 2008, 14:33:00) [MSC v.1500 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more … [View More]

4 11

Fixing code that produces -3 warnings in the Python 2.6 stdlib
by Steven Bethard March 23, 2008

March 23, 2008

On Sun, Mar 23, 2008 at 3:02 PM, "Martin v. Löwis" wrote: [talking about running the buildbots using the -3 flag to issue Py3K warnings] > Yes. I don't think it should be turned on regularly in the tests until > they regularly are quiet under -3. So the plan is to silence all Py3K warnings in the Python 2.6 stdlib? I'd like to see this happen, but I vaguely remembered some people being against this idea, so I'd like to make sure. For what it's worth, I started an issue for this … [View More]

2 1

State of N-dimensional array interface
by Mike Sullivan March 23, 2008

March 23, 2008

What is the current state of the N-D Array Interface proposal (http://numpy.scipy.org/array_interface.shtml). Some work was done on this in an earlier Summer of Code, but it seems to never have been included. Does anybody know what state that work is in and what prevented it's inclusion? (I am interested in completing this as a Summer of Code project. I posted about this on the SOC list, and received a suggestion to try asking python-dev.) -- Mike Sullivan

2 1

Re: [Python-Dev] [Python-checkins] r61796 - in python/trunk: Doc/library/random.rst Lib/random.py Lib/test/test_random.py Misc/NEWS
by Nick Coghlan March 23, 2008

March 23, 2008

> +## -------------------- triangular -------------------- > + > + def triangular(self, low, high, mode): > + """Triangular distribution. > + > + Continuous distribution bounded by given lower and upper limits, > + and having a given mode value in-between. > + > + http://en.wikipedia.org/wiki/Triangular_distribution > + > + """ > + u = self.random() > + c = (mode - low) / (high - low) > + if u &… [View More]

1 0

Distutils patches review request
by Tarek Ziadé March 23, 2008

March 23, 2008

Hi, I would like to make request for a review of three patches: #2385: fixes a run_setup bug, and adds a test_core module, that can be used later to improve core.py coverage (http://bugs.python.org/issue2385) #2461: adds a test_util.py to distutils, to cover util.py. It does not cover byte_compile yet, but others are covered. (http://bugs.python.org/issue2461) #1858 (http://bugs.python.org/issue1858): - makes .pypirc support multiple servers (see http://wiki.python.org/moin/EnhancedPyPI)… [View More]

1 0