Many buildbots are running bsddb 4.7, particularly the debian/ubuntu
ones (4.7.25 which seems to be the latest). Some of them are
crashing, others are not. The max version we support in both 2.6 and
3.0 is 4.7. Should we allow this version or should we use a lower
maximum that is more likely to
On Wed, Jul 30, 2008 at 9:36 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 29, 2008 at 10:07 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>>> +1 OverflowErrors should probably by reserved for numeric overflows.
>>
>> In a sense, passing sys.maxsize as a string size *is* a numeri
On Sun, Apr 13, 2008 at 6:48 AM, Haoyu Bai <[EMAIL PROTECTED]> wrote:
> Gregory P. Smith wrote:
> > -cc: python-dev
> > +cc: python-3000
>
> Thanks for Gregory to point out my mistake and forward this mail to
> python-3000. I really feel sorry for my mistake.
Don't worry about it.
> I have a
> >
> > > >
> > > >
> > > >
> > > > On Sat, Apr 5, 2008 at 7:50 AM, Benjamin Peterson
> > > > <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> &g
I just checked in r62163 with this change:
-rc = os.system(r"ml64 -c -Foms\uptable.obj ms\uptable.asm")
+rc = os.system("ml64 -c -Foms\\uptable.obj ms\\uptable.asm")
What should happen with raw unicode strings that contain a \u? The
old code above was generating:
SyntaxE
On Tue, Apr 1, 2008 at 12:58 AM, Amaury Forgeot d'Arc
<[EMAIL PROTECTED]> wrote:
> On Tue, Apr 1, 2008 at 9:41 AM, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> > I fixed the itertools refleak.
> >
> > test_compile leaks due to code like this:
> >
>
I fixed the itertools refleak.
test_compile leaks due to code like this:
class J:
def foo():
class Bar: pass
I thought Amaury fixed that problem already?
n
On Mon, Mar 31, 2008 at 9:25 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> The current refleaks for 3k are:
>
>
The current refleaks for 3k are:
test_compile leaked [10, 10, 10] references, sum=30
test_io leaked [21, 21, 21] references, sum=63
test_itertools leaked [4, 4, 4] references, sum=12
test_queue leaked [995, 996, 996] references, sum=2987
When running the refleak hunter, 4 tests failed:
test_c
On Fri, Mar 28, 2008 at 9:46 AM, Marcin 'Qrczak' Kowalczyk
<[EMAIL PROTECTED]> wrote:
> Dnia 27-03-2008, Cz o godzinie 11:48 +1200, Greg Ewing pisze:
>
>
> > Tuples are created batchwise because, being immutable,
> > that's the only way to do it. But if set literals are
> > to produce mutable ob
On Fri, Mar 28, 2008 at 3:31 AM, <[EMAIL PROTECTED]> wrote:
>
> Neal> Anything that connects to a remote host is definitely flaky.
>
> Would it maybe help to set up a dedicated host (or virtual host) to serve as
> the sole target of all network tests?
It would help, but not fix the problem.
On Thu, Mar 27, 2008 at 11:31 AM, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > There
> > have been other tests that have also been flaky like test_asynchat,
> > test_smtplib, test_ssl, test_urllib2net, test_urllibnet,
> > test_xmlrpc_net and some of the tests that use networking.
>
> Some of t
On Thu, Mar 27, 2008 at 3:52 AM, Lennart Regebro <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 27, 2008 at 5:33 AM, Talin <[EMAIL PROTECTED]> wrote:
> > -- A document describing the "common subset", and how to write programs
> > in it. This doesn't have to be a complete standalone manual, just an
>
On Wed, Mar 26, 2008 at 5:52 PM, <[EMAIL PROTECTED]> wrote:
> >> The next releases of 2.6/3.0 are planned for April 2, just over a
> >> week from now. There is much work that needs to be done. The
> >> buildbots are in a pretty sad state and the gods are seeing too much
> >> red.
On Wed, Mar 26, 2008 at 9:04 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On Mar 26, 2008, at 8:14 AM, Facundo Batista wrote:
> > 2008/3/26, Neal Norwitz <[EMAIL PROTECTED]>:
> >
> >> We ne
We need to get the tests for Python to be more stable so we can push
out solid releases. In order to achieve this result, we need tests
that are *100% reliable* and fail _only when there is a problem with
Python_. While we aren't nearly as close to that goal as we need to
be, we have to work towa
The next releases of 2.6/3.0 are planned for April 2, just over a week
from now. There is much work that needs to be done. The buildbots
are in a pretty sad state and the gods are seeing too much red.
http://www.python.org/dev/buildbot/stable/
http://www.python.org/dev/buildbot/all/
See my
On Mon, Mar 24, 2008 at 8:10 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Martin v. Löwis schrieb:
>
> >> Since 2.4 Python uses the AST tree to access the future flags. But the
> >> string unicode literals require the information before the AST tree is
> >> created.
> >
> > "We" should ha
On Thu, Mar 20, 2008 at 2:13 AM, Trent Nelson <[EMAIL PROTECTED]> wrote:
> test_getargs2 is failing on Windows x64:
> test test_getargs2 failed -- Traceback (most recent call last):
> File
> "S:\buildbots\python.x64\3.0.nelson-win64\build\lib\test\test_getargs2.py",
> line 190, in test_n
>
[changing to: and subject: ]
On Tue, Mar 18, 2008 at 4:09 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 18, 2008 at 3:58 PM, neal.norwitz
> <[EMAIL PROTECTED]> wrote:
> > Get this test to pass (UserList/UserDict no longer exist and caused a
> skip).
>
> I think the automatic s
On Tue, Mar 18, 2008 at 11:59 AM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Tue, Mar 18, 2008 at 10:49 AM, Aahz <[EMAIL PROTECTED]> wrote:
> >
> > On Tue, Mar 18, 2008, "Martin v. L?wis" wrote:
> > >
> > > When I do a relative star import, I current get
> > >
> > > SyntaxError: 'impor
On Tue, Mar 18, 2008 at 11:17 AM, John Millikin <[EMAIL PROTECTED]> wrote:
> > Possible features for 2.6
> > New modules in the standard library:
> > - JSON implementation
> >
> Have there been any plans made for which one? All of the
No. This was something I added as a nice to ha
On Fri, Feb 22, 2008 at 7:44 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
[... del (tuple, of, variables), etc deleted]
>
> > I also think
> >
> >del a,
> >
> > should not be legal ("SyntaxError: trailing comma not allowed without
> > surrounding parentheses"?), but that's getting
+1 to everything -- n
On Fri, Feb 22, 2008 at 3:45 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everyone,
>
> I've volunteered to be the release manager for Python 2.6 and 3.0.
> It's been several years since I've RM'd a Python release, a
I remember seeing a change which moved the plistlib module from
Lib/plat-mac to Lib so all platforms can use it. This change causes
*all* the builds fail because the test has several problems. For
example, the test references functions/methods that don't exist (see
below). Can someone fix this?
On Nov 1, 2007 7:31 AM, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>
> On 1 Nov, 2007, at 15:22, Guido van Rossum wrote:
>
> > On 11/1/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
> >> I'm volunteering to keep improving PyObjC, but I won't promise that
> >> PyObjC will be complete enough to repla
We've made a lot of progress with the tests. Several buildbots are
green. http://python.org/dev/buildbot/3.0/
There are some tests that are unstable, at least:
test_asynchat test_urllib2net test_xmlrpc
http://python.org/dev/buildbot/3.0/g4%20osx.4%203.0/builds/170/step-test/0
http://python.or
On 10/19/07, Christian Heimes <[EMAIL PROTECTED]> wrote:
>
> I may take it as a challenge to write the view but I don't know if I can
> handle it. I'm still learning how to program C for Python. It may be a
> good opportunity to learn more. If you don't mind that it may take
> longer and if somebod
On 10/16/07, Fred Drake <[EMAIL PROTECTED]> wrote:
> On Oct 16, 2007, at 4:29 PM, Guido van Rossum wrote:
> > I expect this will happen. At the very least, you'll be able to just
> > use 'print' for that function's name if you include
> >
> > from __future__ import print_function
> >
> > at the t
On 10/8/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 10/7/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > - remove locale support from PyString
> > - remove compatibility with PyUnicode from PyString
> > - remove compatibility with PyString from PyUnicode
>
> I'll tackle these myself by
On 8/31/07, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > Does this mean that all the problems you reported at the start of this
> > thread are gone? (If so, I need to remove the link to this thread from
> > the online release notes. :-)
>
> Just the problem with the tim
There are 6 tests that fail on all platforms AFAIK:
3 tests failed:
test_mailbox test_old_mailbox test_unicode_file
3 skips unexpected on linux2:
test_smtplib test_sundry test_ssl
I believe test_smtplib, test_sundry fail for the same reason at least
partially. They can't import email.bas
On 8/29/07, Thomas Wouters <[EMAIL PROTECTED]> wrote:
>
> Am I the only one seeing a refleak in test_io?
I know of leaks in 4 modules, but they all may point to the same one
you identified:
test_io leaked [62, 62] references, sum=124
test_urllib leaked [122, 122] references, sum=244
test_urllib2_
On 8/29/07, Tim Peters <[EMAIL PROTECTED]> wrote:
> [Neal Norwitz]
> > ...
> > We have 4 windows buildbots IIRC, but 2 are offline and there are
> > various problems. Given all the slight variations of Windows, I
> > think it would be good to get another Window
On 8/29/07, David Bolen <[EMAIL PROTECTED]> wrote:
>
> There's an offer of mine to host an additional Windows (win32)
> buildbot, for whatever versions are helpful, in the moderator queue
> for python-dev.
Hmm, that's odd.
> Although in looking at the current 3.0 buildbot
> status page there woul
We got 'em. Let the spam begin! :-)
This page is not linked from the web anywhere:
http://python.org/dev/buildbot/3.0/
I'm not expecting a lot of signal out of them at the beginning. All
but one has successfully compiled py3k though. I noticed there were
many warnings on windows. I wonder i
Py3k is progressing nicely. We are planning the first alpha sometime
this week. The tests are mostly passing. With all the churn over the
last week, I'm sure it's about to change. :-) AFAIK, nearly all the
tests pass on Linux and Mac OS X. There was a report that Windows/VC8
was able to build
Another thing that needs to be ported are the changes to
Lib/test/regrtest.py. Pretty much anything that references ABCs in
there needs backporting. You can verify it works properly by running
regrtest.py with the -R option on any test that uses an ABC. It
should not report leaks. The full comm
On 8/26/07, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote:
> Hello,
>
> It seems that the new I/O system closes the 3 standard descriptors
> (stdin, stdout and stderr) when the sys module is unloaded.
Amaury,
Other than this problem, can you report on how py3k is working on
Windows? How did you
On 8/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I ran 2to3 over the Doc/tools directory. This left a number of problems
> which I initially began replacing manually. I then realized that it would
> be better to tweak 2to3. A couple things I wondered about:
>
> 1. How are we suppos
for this and upload it. All tests
except modulefinder pass (I'm not sure why). There is a hack in
marshal to convert co_code and co_lnotab to a bytes object after
reading in a string.
n
--
>
> On 8/24/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> > On 8/24/07, Neal Norwitz
On 8/24/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> I see in PEP 358 (bytes) http://www.python.org/dev/peps/pep-0358/ that
> marshalling bytes is an open issue and needs to be specified. I'm
> converting code objects to use bytes for the bytecode and lnotab. Is
> there
I see in PEP 358 (bytes) http://www.python.org/dev/peps/pep-0358/ that
marshalling bytes is an open issue and needs to be specified. I'm
converting code objects to use bytes for the bytecode and lnotab. Is
there anything special to be aware of here? It seems like it can be
treated like an non-in
On 8/24/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 8/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Guido> Are there any existing uses (in the core) that are hard to
> > Guido> replace with PyArg_ParseTuple()?
> >
> > There are lots of uses where the arguments aren't
On 8/24/07, Alexandre Vassalotti <[EMAIL PROTECTED]> wrote:
> On 8/24/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> > I suggest merging profile and cProfile (which uses _lsprof) similar to
> > how stringio and pickle are being merged.
>
> cProfile and profil
We ought to clean up the profiling modules. There was a long
discussion about this here:
http://mail.python.org/pipermail/python-dev/2005-November/058212.html
Much of the discussion revolved around whether to add lsprof in the
stdlib. That's been resolved. It was added. Now what do we do?
I
On 8/20/07, Travis E. Oliphant <[EMAIL PROTECTED]> wrote:
>
> > Memory leaked when allocated from:
> > array_buffer_getbuf (arraymodule.c:1775)
> > buffer_getbuf (bufferobject.c:28)
> > bytes_init (bytesobject.c:807)
> > type_call (typeobject.c:429)
>
> Hmm. I'm not sure what memory is being l
On 8/19/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On 8/19/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> > I just fixed a bug in the new memoryview that used PyObject_DEL which
> > caused a problem in debug mode. I had to change it to a Py_DECREF.
> > It se
I just fixed a bug in the new memoryview that used PyObject_DEL which
caused a problem in debug mode. I had to change it to a Py_DECREF.
It seems we have a lot of spellings of ways to free an object and I
wonder if there are more problems lurking in there.
$ cat */*.c | grep -c PyObject_Del
103
$
On 8/18/07, Travis E. Oliphant <[EMAIL PROTECTED]> wrote:
>
> In preparation for the sprints, I have converted all Python objects to
> use the new buffer protocol PEP and implemented most of the C-API. This
> work took place in the py3k-buffer branch which now passes all the tests
> that py3k does
On 8/15/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Georg Brandl schrieb:
> >
> > Neal will change his build scripts, so that the 2.6 and 3.0 devel
> > documentation pages at docs.python.org will be built from these new
> > trees soon.
>
> Okay, I made the switch. I tagged the state of both Pyth
On 8/11/07, Travis E. Oliphant <[EMAIL PROTECTED]> wrote:
>
> However, I'm running into trouble getting it to link. The compilation
> step proceeds fine but then I get a segmentation fault during the link
> stage.
The problem is that python is crashing when trying to run setup.py. I
fixed the im
On 8/11/07, Kurt B. Kaiser <[EMAIL PROTECTED]> wrote:
> I've checked in a version of PyShell.py which directs exceptions to the
> terminal instead of to IDLE's shell since the latter isn't working right now.
>
> There also is apparently an encoding issue with the subprocess setup
> which I'm ignori
On 8/11/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've started a wiki page to catalog known regressions in the py3k
> branch that aren't covered by the test suite:
> http://wiki.python.org/moin/Py3kRegressions.
>
> First up: dir() doesn't work on traceback objects (it now produces
On 8/11/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I see four tests fail that passed yesterday:
>
> < test_csv
> < test_shelve
> < test_threaded_import
> < test_wsgiref
The only failure I could reproduce was test_wsgiref. That problem was
fixed in 56932.
I had updated the previous revisio
On 8/10/07, Talin <[EMAIL PROTECTED]> wrote:
>
> One final thing I wanted to mention, which Guido reminded me, is that
> we're getting short on time. This PEP has not yet been officially
> accepted, and the reason is because of the lack of an implementation. I
> don't want to miss the boat. (The bo
On 8/10/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On 8/9/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> [SNIP]
> > See http://docs.python.org/dev/3.0/results/make-install.out for this
> > failure:
> >
> > Compiling /tmp/python-test-3.0/local/lib/pytho
_check_module
> d2 = run_module(mod_name) # Read from bytecode
> File "/home/neal/python/dev/py3k/Lib/runpy.py", line 72, in run_module
> raise ImportError("No module named %s" % mod_name)
> ImportError: No module named runpy_test
>
> test_textwrap was
I wonder if a lot of the refleaks may have the same cause as this one:
b'\xff'.decode("utf8", "ignore")
No leaks jumped out at me. Here is the rest of the leaks that have
been reported so far. I don't know how many have the same cause.
test_multibytecodec leaked [72, 72, 72] references, sum=
On 8/9/07, Thomas Heller <[EMAIL PROTECTED]> wrote:
> Neal Norwitz schrieb:
> > On 8/9/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> >> This is done. The new py3k branch is ready for business.
> >>
> >> Left to do:
> >>
> >> - s
On 8/9/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> This is done. The new py3k branch is ready for business.
>
> Left to do:
>
> - switch the buildbot and the doc builder to use the new branch (Neal)
I've updated to use the new branch. I got the docs building, but
there are many more problem
On 8/5/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> >> I agree. We should specify that somewhere, so we have a recorded
> >> guideline to use in case of doubt.
> >
> > But where? Time to start a PEP for the C API perhaps?
>
> I would put it into the API documentation. We can put a daily-gener
The wiki seems to be done, so sorry for the spam.
python -v crashes due to infinite recursion (well, it tried to be
infinite until it got a stack overflow :-) The problem seems to be
that Lib/encodings/latin_1.py is loaded, but it tries to be converted
to latin_1, so it tries to load the module,
On 8/2/07, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Neal Norwitz wrote:
> > Since there is a merged int/long type now, we need to decide how the C
> > API should look. For example, should the APIs be prefixed with
> > PyInt_* or PyLong_?
>
> I've alwa
Since there is a merged int/long type now, we need to decide how the C
API should look. For example, should the APIs be prefixed with
PyInt_* or PyLong_? What are the other issues? What do people want
for the C API in 3k?
n
___
Python-3000 mailing lis
__members__ and __methods__ are both deprecated as of 2.2 and there is
the new __dir__. Is there any reason to keep them? I don't notice
anything in PEP 3100, but it seems like they should be removed.
Also PyMember_[GS]et are documented as obsolete and I plan to remove
them unless I hear otherwi
On 7/15/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> When a source file contains a string literal with an out-of-range \U
> escape (e.g. "\U12345678"), instead of a syntax error pointing to the
> offending literal, I get this, without any indication of the file or
> line:
>
> UnicodeDecodeErro
On 6/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > tokenize.TokenError: ('EOF in multi-line statement', (315, 0))
>
> I analyzed that a bit further, and found that
> Lib/distutils/unixccompiler.py:214 reads
>
> if not isinstance(output_dir, (str, type(None)):
>
> This is a syntax error; a
When I originally tried to check in rev 55797, I got this exception:
Traceback (most recent call last):
File "/data/repos/projects/hooks/checkwhitespace.py", line 50, in ?
run_app(main)
File "/usr/lib/python2.3/site-packages/svn/core.py", line 33, in run_app
return apply(func, (pool,)
On 6/5/07, Ron Adam <[EMAIL PROTECTED]> wrote:
> Alexandre Vassalotti wrote:
> > On 6/5/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> >> If "make clean" makes the problem go away, it's usually because there
> >> were old .pyc files with incompatible byte code. We don't change the
> >> .pyc magi
On 5/31/07, Alexandre Vassalotti <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I finished yesterday the implementations of BytesIO and StringIO
> objects in C. They are both fully working. (The code is available in
> my cpy_merge branch in the svn tree.) There is only one thing that is
> bothering me wit
On 5/28/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> Well, I would have complained about that too, except I was too busy
> when splitlines() was snuck into the language behind my back. :-) I
Heh, just today I was wondering if we should kill splitlines:
$ grep splitlines `find Lib -name '*.
On 5/25/07, Greg Ewing <[EMAIL PROTECTED]> wrote:
>
> > Is that OK, because "not not X" should now be spelled "bool(x)", and
> > you haven't allowed the overriding of __bool__?
>
> Yes, I would say that 'not not x' should indeed be spelled
> bool(x), if that's what you intend it to mean.
>
> Whethe
On 5/22/07, Steve Howell <[EMAIL PROTECTED]> wrote:
>
> But since you mentioned conversion, our system is a
> good example of a shop that will be running multiple
> versions of Python side by side for many years. We'll
> cut over new components to Py3k, and then we'll
> gradually upgrade legacy co
On 5/22/07, Guillaume Proux <[EMAIL PROTECTED]> wrote:
> On 5/23/07, Steve Howell <[EMAIL PROTECTED]> wrote:
> > 17.7% of the files I searched have calls to open().
>
> My understand is that the mythical "python 2.x -> 3.0" tool will
> automatically migrate your code by using the AST to find all
>
On 5/22/07, Steve Howell <[EMAIL PROTECTED]> wrote:
>
> In the system I've worked on for the last three years,
> we have at least 200 calls to the builtin open()
> method.
This number is meaningless by itself. 200 calls in how many lines of code?
How many files total and how many files use open?
On 5/22/07, Alexandre Vassalotti <[EMAIL PROTECTED]> wrote:
>
> As you see, cStringIO's code also needs a good cleanup to make it,
> at least, conforms to PEP-7.
Alexandre,
It would be great if you could break up unrelated changes into
separate patches. Some of these can go in sooner rather than
On 5/11/07, Paul Moore <[EMAIL PROTECTED]> wrote:
> On 11/05/07, Greg Ewing <[EMAIL PROTECTED]> wrote:
> > I'm now even more of the opinion that this is too
> > complicated for Python's first generic function system.
> > "If it's hard to explain, it's probably a bad idea."
>
> Hmm. My view is that
I had this problem. make clean solved it. -- n
On 5/8/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> As of r55196 (and possibly earlier), the p3yk branch does not make
> when configured with --with-pydebug. setup.py triggers this assertion
> failure:
>
> python: Objects/object.c:64: _Py_AddToAllO
'/dev/tty'
This seems to only happen when there is no tty associated with a
terminal which happens when run from cron (among other situations).
n
--
On 5/7/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> There are 3* failing tests:
> test_compiler test_doctest test_tran
I'm starting up a continuous build of sorts on the PSF machine for the
3k branch. Right now the failures will only go to me. I've excluded
the two tests that are known to currently fail. This will help us
find new failures (including ref leaks). Probably in a week or so
I'll send the results to
There are 3* failing tests:
test_compiler test_doctest test_transformer
* plus a few more when running on a 64-bit platform
These failures occurred before and after xrange checkin.
Do other people see these failures? Any ideas when they started?
The doctest failures are due to no space at t
On 5/4/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I don't know how the filters for checkin emails are set up, but this
> seems wrong: mail related to the p3yk branch goes to
> python-3000-checkins, but mail related to the py3k-unistr branch goes
> to python-checkins. There are a bunch of bra
On 5/6/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > File "./Parser/asdl_c.py", line 744
> > print(auto_gen_msg, file=f)
>
> I think asdl_c.py should be formulated in a way
> that is compatible with 2.x. It already uses
> f.write in many places; the few remaining ones
> should be updat
On 4/24/07, Emin.shopper Martinian.shopper <[EMAIL PROTECTED]> wrote:
>
> Below are links to the ABC implementation based on meta-classes and
> decorators which I have been using for quite a while.
Emin,
You can get similar functionality by using tools such as pychecker.
PyLint and pyflakes may a
On 4/23/07, Daniel Stutzbach <[EMAIL PROTECTED]> wrote:
>
> The Radical Proposal
> ---
>
> Replace list() with the BList.
I looked over this patch and have various questions/comments. In
rough priority order:
I'm concerned about the moderately heavy use of macros wrt
Can you add refs to all the PEPs?
Will this go into 2.6 also? If so, you should send to python-dev too.
If this is accepted, can you update the 2.6 PEP 361.
On 4/22/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> Implementation
> ==
>
> When the ``-m`` option is used, ``sys.main`` wi
On 4/17/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Apr 17, 2007, at 5:03 AM, Neal Norwitz wrote:
>
> > * maketrans remains (also implemented in stropmodule.c). It is
> > used 11 times.
>
I whacked almost everything in the string (and strop) module. Here
are some things left to do:
* capwords is defined and used only in one place:
./idlelib/testcode.py
ISTM, this can go.
* maketrans remains (also implemented in stropmodule.c). It is used 11 times.
* ascii_letters is
test_cpickle (probably all the same issue here):
test_xpickle, too
==
FAIL: test_ints (test.test_cpickle.cPickleTests)
--
Traceback (most recent call last):
Fil
Can we remove all the functions from the string module that are also
existing methods on string? Then we can figure out what to do with
what's left over?
I'm tempted to ask the same thing about the types module.
TOOWTDI.
n
___
Python-3000 mailing list
CTED]> wrote:
> I'm pretty sure I introduced leaks with the new metaclass code; it was
> a bit of a rush job and there's plenty of new C code. I need a hint on
> how to reproduce this myself for a single test...
>
> On 3/20/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
&
regrtest.py -R 4:3: # on 64-bit, but that might only affect the xpickle error
test_grammar leaked [14, 14, 14] references
test_doctest leaked [84, 84, 84] references
test_ctypes leaked [13, 13, 13] references
test_descrtut leaked [417, 417, 417] references
test_generators leaked [227, 227, 227] r
http://docs.python.org/dev/3.x/
will be updated every hour.
http://docs.python.org/dev/3.x/results/
contains the results of the last build.
n
--
On 3/20/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> I just discovered that the p3yk/ branch can't do a docs build because
> almost none of the cod
-- Forwarded message from python-3000-checkins --
Neal Norwitz schrieb:
> I assume this is not the desired behaviour?
>
>>>> class F:
> ... def __dir__(self):
> ... return [5]
> ...
>>>> dir(F())
> [5]
>>>> f
Did the import magic number get changed? That was the cause of my
last crash in test_hotshot (not related to this though).
n
On 1/10/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Hm, then maybe it started failing after I applied Collin Winter's
> 'except' patches. Collin, does test_hotshot p
On 1/8/07, Anthony Baxter <[EMAIL PROTECTED]> wrote:
>
> Do we also want to warn about use of sq_slice and sq_ass_slice with
> C-code objects? (And yes, my inner 12 year old still giggles about
> sq_ass_slice)
Sometimes it's nice to know you aren't alone. :-)
> My concern is that having to dive i
On 1/7/07, Anthony Baxter <[EMAIL PROTECTED]> wrote:
> I've been thinking a little about how and where we'd add warnings to
> 2.6 and later for things that will break in 3.0. My first idea is
> to add a command line option '-3' (or maybe '-warn3') implemented
> as "from __future__ import py3k". We
On 12/28/06, Tony Lownds <[EMAIL PROTECTED]> wrote:
>
> > * With the modification of MAKE_FUNCTION to be a 32-bit value, this
> > means that EXTENDED_ARG is now used. This means that the peephole
> > optimizer won't work for the outer function. I think we should
> > correct this.
>
> Ok. Somethi
On 1/3/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>
> On 2 Jan, 2007, at 1:14, Brett Cannon wrote:
>
> > * Mac
> >+ applesingle
> >- Undocumented.
> >* AppleSingle is a binary file format for A/UX.
> >+ A/UX no longer distributed.
>
> No problems here.
I
ings like Grammar, obsolete
APIs, etc.
n
On 12/27/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> On 12/27/06, Tony Lownds <[EMAIL PROTECTED]> wrote:
> >
> > On Dec 27, 2006, at 5:31 PM, Guido van Rossum wrote:
> >
> > > I just noticed that PEP 3107 has quiet
1 - 100 of 141 matches
Mail list logo
