On 3/22/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>
> I would love it if PEP 3007 standardised on 4-space indents, the same as the
> standard for Python code in the standard lib. I'd love it even more if
> reindent.py cleaned up C whitespace as well as Python whitespace.
Wait! I thought we were
On 3/28/06, Ian Bicking <[EMAIL PROTECTED]> wrote:
>
> There seems to be a danger that Py3K is seen as a more friendly place to
> suggest changes than Python 2.x (or maybe that the python-3000 list is
> more friendly to these suggestions than py-dev), and so changes are
> brought up here even thoug
On 3/30/06, Terry Reedy <[EMAIL PROTECTED]> wrote:
>
> "Aahz" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > What do we want to tell people who have code like this:
> >
> > keys = d.keys()
> > keys.sort()
>
> Could a good-enough code analyzer detect such, even if separated by
> i
On 3/31/06, Alex Martelli <[EMAIL PROTECTED]> wrote:
>
> So, the fact that (say) Eby or Martelli or the Twisted folks or the
> Zope folks like adaptation, and Ewing or Bicking or (etc ec) dislike
> it, is really a side show. The point that matters, instead, is
> whether GvR likes it or not. From my
On 4/4/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> I'm in agreement with the sentiment of keeping the Python code though
> -- it's incredibly useful for example in Jython and IronPython.
> Perhaps we should switch to a naming scheme where we have a "pickle"
> module that you're supposed to
On 4/7/06, Vineet Jain <[EMAIL PROTECTED]> wrote:
> to have a python restricted exec mode which allows for:
>
> 1. Limit the memory consumed by the script
> 2. Limit access to file system and other system resources
> 3. Limit cpu time that the script will take
> 4. Be able to specify which modules
Is there a benefit to keeping vars()?
"vars([object]) -> dictionary\n\
\n\
Without arguments, equivalent to locals().\n\
With an argument, equivalent to object.__dict__.");
n
___
Python-3000 mailing list
[email protected]
http://mail.python.org/mai
On 4/9/06, Tim Hochberg <[EMAIL PROTECTED]> wrote:
>
> Let me add this cautionary note -- this primarily intended as for
> illustrative purposes. There's a good chance it has bugs. It does,
> however, pass
> test_pprint except for test_subclassing, which it can't really be
> expected to pass.
Py3k
On 4/9/06, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
> Neal Norwitz <[EMAIL PROTECTED]> wrote:
>
> > #3 is easy to do a simple, naive implementation. I don't know what
> > your needs are. If you just want to say "exit this script if it ran
> > more tha
On 4/10/06, Chaz. <[EMAIL PROTECTED]> wrote:
>
> I have thought the approach would work to make a plug-in for Firefox,
> though lacking the time and the knowledge has stopped me from experimenting.
Knowledge should not be an impediment, many of us would be interested
in helping you learn what you
On 4/16/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Some of the coding projects I've recently been proposing as challenges
> to certain wild feature proposals might make good topics for the
> Google Summer of Code (see http://code.google.com/soc/ ).
>
> (I can't volunteer to be a mentor mysel
On 4/16/06, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> again, if my host at Google wants me to spend my working hours being a
> good mentor I could possibly be convinced to make sure I get assigned
> one student (two turned out to be too much). =)
I heard your host is a slave driver and an assho
We've only got a short time to get setup for Google's Summer of Code.
We need to start identifying mentors and collecting ideas for students
to implement. We have the SimpleTodo list
(http://wiki.python.org/moin/SimpleTodo), but nothing on the SoC page
yet (http://wiki.python.org/moin/SummerOfCod
On 4/17/06, Terry Reedy <[EMAIL PROTECTED]> wrote:
>
> The PyPy group also has a few prospective mentors, projects, and mentees.
> On the presumption that PSF coordinating sponsership is not limited to
> CPython only projects, I forwarded Neal's SoC py-dev post to their list.
Excellent. I was thi
rences that are known on python-dev to vouch
for them.
Terry are you interested in being a mentor?
n
(*) Unknown to me I guess, since I'm currently the only approver of mentors.
--
On 4/17/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> On 4/17/06, Terry Reedy <[EMAIL PROTECTED]>
On 4/17/06, Terry Reedy <[EMAIL PROTECTED]> wrote:
>
> Your next post answered my question as to mentor eligibility: known of by
> you or two references therefrom. But back to project eligibility: how far
> beyond direct implementation-related projects? How about progammer support
> like pylint/p
entations,
> programmer utilitilies, libraries, packages, or frameworks. Project ideas
... or frameworks related to Python
> People interested in mentoring a student though PSF are encouraged to
> contact Neal Norwitz at [EMAIL PROTECTED] People unknown to Neal or
> Guido should find a coupl
s
> currently requesting mentors, not students. Perhaps
>
>Subject: Python Software Foundation looking for mentors for the
> Google Summer of Code
>
> would work?
>
> How widely are you sending this? I'd say c.l.py.a, c.l.py, python-dev,
> IronPython, Jython,
On 4/19/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> I recommend profiling. I seem to recall that last time we did this, we
> found that creating the frame object is a significant cost factor.
That's part of it. Plus there's a tuple allocation (and copy).
n
___
On 4/19/06, Terry Reedy <[EMAIL PROTECTED]> wrote:
>
> My revision is both pasted below and attached as a text file. I am not
> posting because I prefer you send the original after one more check and
Thanks Terry. I sent it.
Everyone feel free to spread the word.
n
Blake,
What problems did you have? There is a patch or two up on SF that
address some of the issues.
I know of some problems, but we don't have a volunteer to work on
these issues. So if you could be that volunteer, maybe we could solve
this problem. Not for 3.0 in the future, but for 2.5 toda
There's a new SoC mailing list.
[EMAIL PROTECTED]
You can sign up here: http://mail.python.org/mailman/listinfo/soc2006
This list is for any SoC discussion: mentors, students, idea, etc.
Student can submit applications starting May 1, so now is the time to
get students interested in your
If you move forward with this, please review (learn from and steal the
best parts of) the ACE APIs. http://cs.wustl.edu/~schmidt/ACE.html
They've done a lot of work in this area and have a lot of experience.
It would also be good to talk to the twisted guys.
We should also support epoll beyond
On 4/30/06, Bill Janssen <[EMAIL PROTECTED]> wrote:
> I've looked over the PyGUI code a bit more carefully.
>
> It still looks good to me as a Py3K standard portable GUI candidate.
> In particular, it doesn't look like it would be hard to port to Java
> Swing (for Jython) and Windows.Forms (for Iro
On 5/2/06, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
>
> I think Guido had the best solution. Use set() for empty sets, use {}
> for empty dicts, use {genexp} for set comprehensions/displays, use
> {1,2,3} for explicit set literals, and use {k1:v1, k2:v2} for dict
> literals. We can always add
There is less than a week left before students must submit a final
application. There are a bunch of ideas up on the wiki:
http://wiki.python.org/moin/SummerOfCode/
The wiki has instructions for how to submit a proposal. There are
many different areas including: core language features, lib
On 5/10/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> Regarding the question what to do if something un-annotated is passed,
> you could have a strict and a lenient mode, sort of the equivalents of
> guilty-unless-proven-innocent and innocent-unless-proven-guilty. I
> guess the latter is more
On 5/23/06, Talin <[EMAIL PROTECTED]> wrote:
> Well, c.l.p was strangely quiet in response to my posting PEP 3102 a few
> days ago. Only two comments, one of a general "ick" variety that seems
> mainly based on personal bias, and another which likes the idea but
> votes a -1 on the 'naked star' syn
On 5/31/06, Collin Winter <[EMAIL PROTECTED]> wrote:
>
> All in all, the tuple->list change was minimally invasive.
>
> Overall, I've chosen to keep the external interfaces of the changed
> modules/packages the same; if there's a desire to change them later,
> this SVN commit can be used to figure
On 8/20/06, Osvaldo Santana <[EMAIL PROTECTED]> wrote:
> On 8/20/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > Excellent! I'm adding Brett to the CC's.
>
> Cool. Has Brett planned something to this rewrite?
I'm not sure exactly what you are asking. It's mostly planned to be a
re-implementat
On 8/24/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
>
> (which reminds me that speeding up handling of optional arguments to C
> functions
> would be an even better use of this energy)
If this patch: http://python.org/sf/1107887 is integrated with some
of my current work, it should do the job n
On 9/1/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> just noticed that PEP 3100 says that PyString_AsEncodedString and
> PyString_AsDecodedString is to be removed, but it doesn't mention
> any other PyString (or PyUnicode) functions.
>
> how large changes can we make here, really ?
I don't know i
On 9/12/06, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
>
> We could always rename raw_input() to input(). Just a thought. . .
>
> D'oh. Guido already said he doesn't like that idea :)
>
> FWIW, I think it is a good idea. If there is a little 2.x vs 3.0
> confusion, so be it. The use of inpu
On 11/3/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Greg Ewing wrote:
>
> > Besides, the BDFL is going to do whatever he wants
> > anyway, so let's just leave him to get on with it. :-)
>
> but where is he? has anyone seen him lately ?
Sure, he's been busy at work and sick recently. He'll pro
In looking at this and some other stuff, I thought about this code:
x = 1,
How about requiring parens around (1,)? It kinda sucks to make it
inconsistent by only requiring parens for singleton tuples. But it
might prevent more errors and make it much harder to miss the comma.
I got this idea w
What do we want to do with the current versionadded/versionchanged
markups in the doc for 3k? Should we remove all references to 1.x
changes? all 2.x changes? Keep them? all of them?
Given we are trying to clean things up, I think I'd prefer to remove
all the old references to 1.x/2.x changes.
On 12/19/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I've written a quick version of PEP 3106, which expresses my ideas
> about how the dict methods to access keys, values and items should be
> redone.
>
> The text is in svn:
> http://svn.python.org/view/peps/trunk/pep-3106.txt?rev=53096&view
On 12/19/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 12/19/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
> > Okay, I updated the patch at SF. While you're at it, in PEP 3100 there's
> > "compile(): put in sys (or perhaps in a module of its own)". I guess that
> > isn't really necessary eithe
On 12/19/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 12/18/06, Brett Cannon <[EMAIL PROTECTED]> wrote:
> [me]
> > > Well, what do you think of my pronouncement in response to Thomas's
> > > mail (just rename a bunch of things that don't conform to our own
> > > naming standard)? That shoul
Some of these have already been fixed in a version sent to me. I need
to check that version in. I haven't reviewed it, but I believe it
addresses the __signature__ issue. I should have time to get this in
tonight.
n
--
On 12/27/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I just noticed t
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 quietly been checked in. Thanks
> > Collin and Tony!
>
> Ok, updated (and sent to Neal for checkin, thanks Neal!)
I just checked in a slightly modifie
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
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?
+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
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
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 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
[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 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
>
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
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
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
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
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 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 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 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 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
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
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:
>
>
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 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 Sat, Apr 5, 2008 at 7:50 AM, Benjamin Peterson
> > > > <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> &g
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 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
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 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
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/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 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
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
-- 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
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
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
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:
&
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
test_cpickle (probably all the same issue here):
test_xpickle, too
==
FAIL: test_ints (test.test_cpickle.cPickleTests)
--
Traceback (most recent call last):
Fil
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
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.
>
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/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
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 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 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
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
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
'/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 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
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
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/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, 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:
>
> 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/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/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/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 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
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/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
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
1 - 100 of 141 matches
Mail list logo
