itself.
I've needed to do this a few times when wrapping libraries.
Michael Foord
With classic classes, this is trivial, since __getattr__ is always
consulted, even for retrieval of special methods.
With new-style classes, however, the __getattribute__ machinery can be
bypassed, meaning the
orm X".
And what about platforms like the JVM or CLR?
Incidentally there were a small but vocal group of Pythonistas who were
(are?) certain that IronPython is not Python because it doesn't have
[all of...] the C extensions.
Michael Foord
Skip
James Y Knight wrote:
On May 21, 2008, at 11:26 AM, Michael Foord wrote:
And what about platforms like the JVM or CLR?
Incidentally there were a small but vocal group of Pythonistas who
were (are?) certain that IronPython is not Python because it doesn't
have [all of...] the C exten
. Installing Mono is pretty much
'one click' these days and it *comes* with IronPython (and has done for
a while). I'm writing "IronPython in Action" on the Mac. Solaris I don't
care about... :-)
Michael Foord
Skip
___
. To have a proxy where:
proxy_instance += 1
unwraps the proxy is really no good! (At least not for my use cases...)
Michael Foord
--
http://www.ironpythoninaction.com/
http://www.theotherdelia.co.uk/
http://www.voidspace.org.uk/
http://www.ironpython.info/
http://www.resolverhacks.net
some code duplication with other parts of the standard library
may still remain in 2.6/3.0).
+1 from me as well.
I think multiple-processes is over played as a concurrency solution in
Python (where you need to marshal lots of data in and out, the overheads
of multiple processes can be very expens
class?
>>> class X(object):
... def __unicode__(self):
... return 'fish'
... __str__ = __repr__ = __unicode__
...
>>> x = X()
>>> open(x)
Traceback (most recent call last):
File "", line 1, in
TypeError: coercing to Unicode: nee
ting with %s and a single object or a tuple meets
>90% of my string formatting needs.
Michael Foord
Cheers,
Nick.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.or
over.
But that either needs doing for 3.0 or waiting until 4.0 right?
Personally I only *occasionally* find the tuple interpolation a problem
and am perfectly happy with the current % string formatting...
Michael Foord
Cheers,
Nick.
___
Pytho
it that
assignment to None is disallowed and the naming of members called None
being invalid syntax is merely an artefact of the implementation of
this, or does Python require this...
Michael Foord
In a similar fashion:
class Parrot(object):
... pass
...
p = Parrot()
p.
m but the DLR 'catches' attribute look ups etc
to add Python methods to basic types and do 'other magic' like wrapping
Python functions as delegates).
This at least enshrines the current IronPython behaviour with the veneer
of respectability.
Michael Foord
Alex
On Mo
illip J Eby but can't find a reference easily). The last one I
wrote was to proxy CPython objects from IronPython via Python.NET...
I would prefer it if the proxy class wrapped the return values of
inplace operations.
Michael Foord
I've pushed as hard as I'm personally willin
illip J Eby but can't find a reference easily). The last one I
wrote was to proxy CPython objects from IronPython via Python.NET...
I would prefer it if the proxy class wrapped the return values of
inplace operations.
Michael Foord
I've pushed as hard as I'm personally willin
y probably needs at least clarifying now
that Python does have a 'with' statement.
Michael Foord
--
http://www.ironpythoninaction.com/
http://www.theotherdelia.co.uk/
http://www.voidspace.org.uk/
http://www.ironpython.info/
http://www.resolverhacks.net/
performance
of a Python implementation is not that great.
I'm +1 - but this proposal has been made many times before and people
always argue about what features are needed or desirable. :-(
Michael Foord
To fight that problem I want to proposed a new class in "collections&quo
Hello all,
I'm just doing some housekeeping on a Windows install, and notice that
the 'Publisher' of my Python 2.4 and 2.5 installs is shown as "Martin v.
Lowis". Whilst I *personally* find this very reassuring I wonder if this
is intended / ideal?
All
Michael Foord wrote:
Hello all,
I'm just doing some housekeeping on a Windows install, and notice that
the 'Publisher' of my Python 2.4 and 2.5 installs is shown as "Martin
v. Lowis". Whilst I *personally* find this very reassuring I wonder if
this is intended /
y case, bug #1737210 complained about it, and I changed it to
"Python Software Foundation". I can't retroactively change it for the
releases you are looking at.
No problem. I was more concerned about future releases.
All the best,
Michael Foord
Regards,
Martin
-
Antoine Pitrou wrote:
Let's split hairs a little...
Steve Holden holdenweb.com> writes:
"Fail" isn't a negative. As Guido said, it's a description of the test
behavior under particular circumstances.
In most circumstances, "fail" is a negative word defined as the contrary of
somethin
tely my writing commitment is going to keep me occupied until
August - after which it will be one of my highest priorities.
Michael Foord
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/
http://www.trypython.org/
http://www.ironpython.info/
http://www.theotherdelia.co.uk/
h
weren't controversial but I might not get to:
assertRaisesWithMessage taking a regex to match the error message
expect methods that collect failures and report at the end of the test
(allowing an individual test method to raise several errors without stopping)
assertIsInstan
Raymond Hettinger wrote:
Michael Foord <[EMAIL PROTECTED]> writes:
The full list of changes proposed (feel free to start - but ping me or
the list) and not shot down was something like:
[…]
Thanks. I'm working these into another draft PEP that I hope to have
up in a day or two.
Ben Finney wrote:
[snip..]
Remove redundant names
--
The following attribute names exist only as synonyms for other names.
They are to be removed, leaving only one name for each attribute in
the API.
``TestCase`` attributes
~~~
* ``assertEqual``
* ``ass
Raymond Hettinger wrote:
From: "Ben Finney" <[EMAIL PROTECTED]>
Right, so I'm putting up a separate PEP just for the renaming. Should
be arriving on this list soon.
I would like to work with you or someone else who is interested
on an alternative PEP for a separate, simpler test module
using t
Raymond Hettinger wrote:
From: "Ben Finney" <[EMAIL PROTECTED]>
Right, so I'm putting up a separate PEP just for the renaming. Should
be arriving on this list soon.
I would like to work with you or someone else who is interested
on an alternative PEP for a separate, simpler test module
using t
Benjamin Peterson wrote:
On Mon, Jul 14, 2008 at 6:18 PM, Ben Finney <[EMAIL PROTECTED]> wrote:
"Benjamin Peterson" <[EMAIL PROTECTED]> writes:
On Mon, Jul 14, 2008 at 8:25 AM, Ben Finney <[EMAIL PROTECTED]> wrote:
Use new-style classes throughout
--
Raymond Hettinger wrote:
``set_up(…)``
Replaces ``setUp(…)``
. .
``tear_down(…)``
Replaces ``tearDown(…)``
Am I the only one who finds this sort of excessive pep-8 underscoring
to be horrorific?
Nobody I know spells setup and teardown as two words. I dread using
the module with these ne
vel attributes just for the duration of the test.
As we're changing more of our tests over to use these we're finding it
reduces the volume and complexity of our test code.
Michael Foord
[1] Based on http://code.google.com/p/mock/ although there is some
outstandi
Collin Winter wrote:
On Tue, Jul 15, 2008 at 6:58 AM, Ben Finney <[EMAIL PROTECTED]> wrote:
Backwards Compatibility
===
The names to be obsoleted should be deprecated and removed according
to the schedule for modules in PEP 4 [#PEP-4]_.
While deprecated, use of the depreca
M.-A. Lemburg wrote:
On 2008-07-16 10:14, Ben Finney wrote:
"M.-A. Lemburg" <[EMAIL PROTECTED]> writes:
Since this is a major change in the unit test API, I'd also like
to suggest that you use a new module name.
This is both a precaution to prevent tests failing due to not having
been upgrade
Terry Reedy wrote:
Michael Foord wrote:
Collin Winter wrote:
Is any provision being made for a 2to3 fixer/otherwise-automated
transition for the changes you propose here?
As the deprecation is intended for 2.X and 3.X - is 2to3 fixer needed?
A fixer will only be needed when it
Brett Cannon wrote:
On Tue, Jul 15, 2008 at 7:05 PM, Ben Finney <[EMAIL PROTECTED]> wrote:
Scott Dial <[EMAIL PROTECTED]> writes:
Why [introduce redundant test names]?
assert_not_less_than = assert_greater_than_or_equal
assert_not_greater_than = assert_less_than_or_equal
assert_not_le
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M.-A. Lemburg wrote:
On 2008-07-16 02:20, Collin Winter wrote:
On Tue, Jul 15, 2008 at 6:58 AM, Ben Finney <[EMAIL PROTECTED]> wrote:
Significant updates include removing all reference to the
(already-resolved) ne
Guido van Rossum wrote:
Having skimmed much material about proposed changes to the venerable
unitest module, I'd like to set some boundaries. PEPs that don't
follow the following rules are very unlikely to be accepted.
1. The API is not going to be renamed to PEP-8 conformance. This
notwithstand
Raymond Hettinger wrote:
From: "Michael Foord" <[EMAIL PROTECTED]>
I assume this doesn't rule out the addition of [some of..] the new
convenience test methods?
In Kent Beck's book on Test Driven Development, he complains that most
unittest implementations spawned f
C. Titus Brown wrote:
[snip..]
Paranthetically, wrt unittest, the world seems to be divided into two
kinds of people : those who find the current API uninspiring but ok, and
those who absolutely hate it. Has anyone said that they *love* the
current unittest API with all of its boilerplate? If n
C. Titus Brown wrote:
On Wed, Jul 16, 2008 at 02:15:29PM -0700, C. Titus Brown wrote:
-> At this point I might suggest taking a look at the nose and py.test
-> discovery rules and writing a simple test discovery system to find &
-> wrap 'test_' functions/classes and doctests in a unittest wrapper
://www.python.org/dev/peps/pep-3126/
Michael Foord
Regards,
Stavros Korokithakis
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/fuzzy
Maciej Fijalkowski wrote:
You can provide selfless class as a class with special metaclass that
overloads __new__ and changes signature of each method. Not sure how
good is this, but requires no changes to the language and will work as
you want.
Are you advocating this Maciej? ;-)
There's
Georg Brandl wrote:
Fredrik Lundh schrieb:
(using 3.0a4)
>>> exec(open("file.py"))
Traceback (most recent call last):
File "", line 1, in
TypeError: exec() arg 1 must be a string, file, or code object, not
TextIOWrapper
so what's "file" referring to here?
(the above works under 2.5,
ct.__reversed__
Michael Foord
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/
http://www.trypython.org/
http://www.ironpython.info/
http://www.theotherdelia.co.uk/
http://www.resolverhacks.net/
___
Python-Dev mailing list
Python-Dev@
M.-A. Lemburg wrote:
On 2008-08-28 21:31, Michael Foord wrote:
Hello all,
The documentation for __hash__ seems to be outdated. I'm happy to submit
a patch, so long as I am not misunderstanding something.
http://docs.python.org/dev/reference/datamodel.html#object.__hash__
The document
Hello Kim,
Thanks for your post. The source code control used for Python is Subversion.
Patches submitted to this list will unfortunately get lost. Please post
the bug report along with your comments and patch to the Python bug tracker:
http://bugs.python.org/
Michael Foord
Kim Gräsman
Maciej Fijalkowski wrote:
Hello,
I'm a little clueless about exact semantics of following snippets:
http://paste.pocoo.org/show/85698/
is this fine?
It looks right to me. :-)
In the first case the NameError is caught by the except and not
re-raised (but still enters the finally after th
Martin v. Löwis wrote:
- Is anyone already working on this? I know that Brad Clements made an attempt
some years ago but didn't get it integrated, are there any others? Maybe even
any ongoing work?
My understanding is that Python works fairly well on CE as-is, so no
significant patches ar
on ctypes would be
enormously useful for PyPy, IronPython and Jython, but ctypes is not yet
as portable as Python itself which could be an issue (although one worth
resolving).
Michael Foord
[1] http://code.google.com/p/ironclad
[2] Strictly speaking they are managed objects of unmanaged t
ems) simply turn to other languages.
All the best,
Michael Foord
I worry, if it is ever actually removed, that I won't be able to
convince these people that you really don't need to spawn twenty
threads to write an IRC bot.
On Fri, Oct 31, 2008 at 2:24 AM, Nick Coghlan <[EMA
Martin v. Löwis wrote:
> While I'm happy that Barry has automated his part to a high degree,
> my part is, unfortunately, much less automated. I could personally
> automate the build process a bit more, but part of it is also testing
> of the installers, which is manual.
Maybe you could dele
:-)
It would work well with the files being generated from an XML templating
language like Mako which is what we will be switching to at Resolver
Systems.
http://wix.sourceforge.net/
Michael Foord
I'm sure the
Python Software Foundation would easily get a free license of one of
his really belongs on Python-ideas and not Python-dev.
The main reason why not is that someone(s) from the Python core team
would then need to 'own' maintaining Psyco (which is x86 only as well).
Psyco is so hard to maintain that even the original author wants to drop
it. :-)
Mich
Lennart Regebro wrote:
On Fri, Dec 12, 2008 at 02:13, Sturla Molden wrote:
I genuinely think the use of threads should be discouraged. It leads to
code that are full of bugs and difficult to maintain - race conditions,
deadlocks, and livelocks are common pitfalls.
The use of threads f
Leif Walsh wrote:
On Sat, Dec 20, 2008 at 3:04 PM, M.-A. Lemburg wrote:
These long exit times are usually caused by the garbage collection
of objects. This can be a very time consuming task.
In that case, the question would be "why is the interpreter collecting
garbage when it knows w
Brett Cannon wrote:
OK, since no one has really said anything, I am going to assume no one
has issues with importlib in terms of me checking it in or choosing a
name for it (I like importlib more than imp so I will probably stick
with that).
So I will do some file renaming and reorganization, ge
Victor Stinner wrote:
Hi,
Le Wednesday 14 January 2009 12:23:46 Kristján Valur Jónsson, vous avez
écrit :
socket.create_connection() trying to connect to ("localhost", port)
(...)
return an AF_INET6 entry before the AF_INET one and try connection
to that. This connect() attemt fails after
o make the changes permanent
unless they are particularly intrusive.
Michael Foord
Alternatively, is it reasonable to create a new branch solely
for the purpose of tracking down one particular problem?
Again, I don't see this sort of thing happening, but it seems
like an attractive strategy, since it a
) and this is presumed to
apply to parts of software like header files and interface descriptions
- which could easily apply to ABCs in Python.
I recommend his book by the way - I'm about half way through so far and
it is highly readable
Michael Foord
--
http://www.ironpythonin
Brett Cannon wrote:
On Mon, Jan 19, 2009 at 19:02, Scott Dial
wrote:
Brett Cannon wrote:
3. Are brackets for optional arguments (e.g. ``def fxn(a [, b=None [,
c=None]])``) really necessary when default argument values are
present? And do we really need to nest the brackets when it is o
Tim Lesher wrote:
On Tue, Jan 20, 2009 at 08:02, Luke Kenneth Casson Leighton
wrote:
of course - if python for win32 ENTIRELY DROPPED msvc as a development
platform, and went for an entirely free software development
toolchain, then this problem goes away.
That's a non-starter for any
Stephen J. Turnbull wrote:
M.-A. Lemburg writes:
> On 2009-01-20 11:02, Michael Foord wrote:
> > Mere collections of facts are not copyrightable as they are not
> > creative (the basis of copyright)
That's incorrect in the U.S.; what is copyrightable is an *original
work
Brett Cannon wrote:
On Sun, Jan 25, 2009 at 10:37, "Martin v. Löwis" wrote:
There's a possible third way. I've heard (though haven't investigated)
that some people are working on supporting the svn wire protocol in the
bzr server. This would mean that anybody who's still comfortable with
s
27;t think we do users any favours by being cautious in removing /
fixing things in the 3.0 releases.
Michael Foord
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.py
for Python 2.7, too.
Don't we have a pretty-print API - and isn't it spelled __str__ ?
Michael Foord
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.py
Raymond Hettinger wrote:
From: "Guido van Rossum"
On the one hand I understand that those folks want a stable target. On
the other hand I think they would prefer to find out sooner rather
than later they're using stuff they shouldn't be using any more. It's
a delicate balance for sure, and I ce
TIME
> technically inaccurate?
>
It does mean that users will expect to be able to call with an explicit
timeout=None and get the default behaviour. Just use the numeric value of the
global timeout perhaps?
MIchael Foord
> FWIW, I see similar style (...,[,timeout], kw=val) adopte
On 3 Aug 2011, at 21:36, Ethan Furman wrote:
> My apologies for posting here first, but I'm not yet confident enough in my
> bug searching fu, and duplicates are a pain.
>
> Here's the issue:
>
> from unittest import *
That's the bug right there. Just import TestCase and main and everything sh
On 3 Aug 2011, at 22:58, Ethan Furman wrote:
> Michael Foord wrote:
>> On 3 Aug 2011, at 21:36, Ethan Furman wrote:
>>> My apologies for posting here first, but I'm not yet confident enough in my
>>> bug searching fu, and duplicates are a pain.
>>>
>
is too late for Python 2.x, it *is* (in my opinion) worth removing
unused and unneeded APIs. Even if the effort to remove them is more than any
effort saved on the part of users it helps other implementations down the road
that no longer need to provide these APIs.
All the best,
Michael Foord
On 6 Sep 2011, at 20:36, Steven D'Aprano wrote:
> Terry Reedy wrote:
>> On 9/6/2011 12:58 PM, Tres Seaver wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 09/06/2011 12:59 PM, Stephen J. Turnbull wrote:
Joao S. O. Bueno writes:
> Removing it would mean explici
On 6 Sep 2011, at 21:18, Martin v. Löwis wrote:
>>> Perhaps I missed something early on, but why are we proposing
>>> removing a function which (presumably) is stable and tested and
>>> works and is not broken? What maintenance is needed here?
>>
>>
>> The maintenance burden is on other implement
On 08/09/2011 03:46, Stephen J. Turnbull wrote:
Glyph Lefkowitz writes:
> On Sep 7, 2011, at 10:26 AM, Stephen J. Turnbull wrote:
>
> > How about "title"?
>
> >>> 'content-length'.title()
> 'Content-Length'
>
Does anyone *actually* use .title() for this? (And why not just
whole branch.
This works pretty well.
All the best,
Michael Foord
Another question: What about the docs? Can we just point people to
docs.python.org and tell them to mentally replace packaging with
distutils2? If that is judged unacceptable, then I’ll synchronize the
docs in the d2 repo, but t
On 15/09/2011 17:23, Éric Araujo wrote:
Le 13/09/2011 18:34, Michael Foord a écrit :
On 13/09/2011 16:57, Éric Araujo wrote:
(IIRC PyPI will require us to play games to have both
2.x and 3.x versions of distutils2.)
What I'm doing for unittest2.
[...]
2) I have a pypi project c
On 21/09/2011 18:02, Stephen J. Turnbull wrote:
Georg Brandl writes:
> I don't think so. "skip if not" reads pretty well for me, while I
> always have to think twice about "unless" -- may be a non-native-
> speaker thing.
FWIW, speaking as one native speaker, I'm not sure about that.
xception
do_something()
All the best,
Michael Foord
Thanks
Wilfred
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/fuzzyman%40vo
On 27/09/2011 19:59, Laurens Van Houtven wrote:
Sure, you just *do* it. The only advantage I see in assertNotRaises is
that when that exception is raised, you should (and would) get a
failure, not an error.
There are some who don't see the distinction between a failure and an
error as a useful
On 04/10/2011 02:20, Brian Curtin wrote:
On Mon, Oct 3, 2011 at 18:32, Ryan Wells (MP Tech Consulting LLC)
mailto:v-ry...@microsoft.com>> wrote:
Hello Python Developers,
I am a Program Manager with the Ecosystem Engineering team at
Microsoft. We are tracking a issue with Python 3.2
On 08/10/2011 00:19, Terry Reedy wrote:
On 10/7/2011 6:18 AM, Glyph wrote:
To sum up what I believe is now the consensus from this thread:
1. Anyone setting up a buildslave should take care to invoke the build
in an environment where an out-of-control buildbot, potentially
executing a
support for older
versions of python at will.
Ditto. unittest2 and the mock test suite both have a subset of this in
for some of the newer Python standard library features they use (plus
putting back into Python 3 some of the things that disappeared like
callable and apply).
All the best,
Mic
On 9 Oct 2011, at 21:14, Paul Moore wrote:
> On 9 October 2011 20:47, Tarek Ziadé wrote:
>> On Sun, Oct 9, 2011 at 9:31 PM, PJ Eby wrote:
>> ...
What we can do however
is to see what bdist_egg does and define a new bdist command inspired by
it, but without zipping, pkg_resource cal
+ features then projects that also
support Python 3 can still use new features without having to worry
about compatibility (it solves the same problem).
All the best,
Michael Foord
--- Giampaolo
http://code.google.com/p/pyftpdlib/
http://code.google.com/p/psutil/
__
been backported to Python 2.4
(although use of the with statements in the tests themselves will have
to be changed still).
All the best,
Michael Foord
-Toshio
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
Hey folks,
The title of the "Global Module Index" for 3.2 documentation is "Python
3.1.3 documentation".
http://docs.python.org/py3k/modindex.html
See the report below (attached screenshot removed).
All the best,
Michael Foord
Original Message
Subjec
lass__
There must be something else going on here.
All the best,
Michael Foord
Thanks and regards,
Vinay Sajip
[1] http://goo.gl/1Jlbj
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe
On 19 November 2011 23:11, Vinay Sajip wrote:
> Michael Foord voidspace.org.uk> writes:
>
> > That works fine in Python 3 (mock.Mock does it):
> >
> > >>> class Foo(object):
> > ... @property
> > ... def __class__(self):
> > ... retur
stand correctly, ABCs are great for allowing classes of objects to
pass isinstance checks (etc) - what proxy, lazy and mock objects need is to be
able to allow individual instances to pass different isinstance checks.
All the best,
Michael Foord
> --Guido
>
> On Sat, Nov 19, 2011 at 6
On 20/11/2011 21:41, Guido van Rossum wrote:
On Sun, Nov 20, 2011 at 10:44 AM, Michael Foord
wrote:
On 20 Nov 2011, at 16:35, Guido van Rossum wrote:
Um, what?! __class__ *already* has a special meaning. Those examples
violate that meaning. No wonder they get garbage results.
The correct
On 25/11/2011 00:20, Jesus Cea wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When mailing there, I get this error. Not sure where to report.
The address works fine. It would be nice if someone fixed the annoying
bounce however. :-)
Michael
"""
Final-Recipient: rfc822; sdr...@sdrees
On 25/11/2011 15:48, Paul Moore wrote:
On 25 November 2011 15:07, Amaury Forgeot d'Arc wrote:
2011/11/25 Paul Moore
It would be nice to have the optimisation back if it's easy enough to
do so, for quick-and-dirty code, but it is not a good idea to rely on
it (and it's especially unwise to base
On 24 Nov 2011, at 04:06, Nick Coghlan wrote:
> On Thu, Nov 24, 2011 at 10:28 AM, Guido van Rossum wrote:
>> Mea culpa for not keeping track, but what's the status of PEP 380? I
>> really want this in Python 3.3!
>
> There are two relevant tracker issues (both with me for the moment).
>
> The
On 26/11/2011 07:46, Maciej Fijalkowski wrote:
On Sat, Nov 26, 2011 at 6:39 AM, Nick Coghlan wrote:
On Sat, Nov 26, 2011 at 8:14 AM, Michael Foord
wrote:
On 24 Nov 2011, at 04:06, Nick Coghlan wrote:
On Thu, Nov 24, 2011 at 10:28 AM, Guido van Rossum wrote:
Mea culpa for not keeping
APIs around can require effort just to keep them
working and may actively *prevent* other changes / improvements.
All the best,
Michael Foord
So, I think we should have a clear and working deprecation policy, and
Ezio's suggestion sounds good to me. There should be a clean way to
state, i
issue it's
not clear to me what needs to be done for it to be accepted (or rejected),
beyond a general "it's a big change".
All the best,
Michael Foord
--
http://www.voidspace.org.uk/
May you do good and not evil
May you find forgiveness for yourself and forgive others
On 9 Dec 2011, at 15:13, Barry Warsaw wrote:
> On Dec 09, 2011, at 09:20 AM, Martin v. Löwis wrote:
>
>> One use case (and the only one I'm aware of) is to pass keyword
>> parameters. Python 2 insists that they are str (and doesn't accept
>> unicode), Python 3 insists that they are str (and does
On 13/12/2011 13:33, Laurence Rowe wrote:
On Mon, 12 Dec 2011 22:18:40 +0100, Chris McDonough
wrote:
On Mon, 2011-12-12 at 09:50 -0500, PJ Eby wrote:
As someone who ported WebOb and other stuff built on top of it
to Python
3 without using "from __future__ import uni
something else?
Michael
--
Nick Coghlan (via Gmail on Android, so likely to be more terse than usual)
On Dec 13, 2011 11:46 PM, "Michael Foord" <mailto:fuzzy...@voidspace.org.uk>> wrote:
On 13/12/2011 13:33, Laurence Rowe wrote:
On Mon, 12 Dec 2011 22
On 13/12/2011 14:28, Laurence Rowe wrote:
On Tue, 13 Dec 2011 14:42:12 +0100, Michael Foord
wrote:
On 13/12/2011 13:33, Laurence Rowe wrote:
On Mon, 12 Dec 2011 22:18:40 +0100, Chris McDonough
wrote:
On Mon, 2011-12-12 at 09:50 -0500, PJ Eby wrote:
As someone who ported WebOb
On 13/12/2011 21:10, Terry Reedy wrote:
On 12/13/2011 2:02 PM, PJ Eby wrote:
On Tue, Dec 13, 2011 at 11:24 AM, Antoine Pitrou mailto:solip...@pitrou.net>> wrote:
On Tue, 13 Dec 2011 15:28:31 +0100
"Laurence Rowe" mailto:l...@lrowe.co.uk>> wrote:
>
> The approach that most people seem to
still supporting 2.4. The *major* syntax feature you lose
by targeting 2.4 is the with statement, so it will be nice to drop 2.4 support.
The next releases of mock and unittest2 will still support 2.4, but the ones
after that will be 2.5+.
Thankfully tox makes testing across multiple versions
for research projects. They switched to using Python 3 a while ago.
All the best,
Michael Foord
> Mark
>
> On 21/12/2011 6:16 PM, Chris Withers wrote:
>> What's the python-dev view on this?
>>
>> Original Message
>> Subject: Anyone still
Hello all,
A paper (well, presentation) has been published highlighting security problems
with the hashing algorithm (exploiting collisions) in many programming
languages Python included:
http://events.ccc.de/congress/2011/Fahrplan/attachments/2007_28C3_Effective_DoS_on_web_applicatio
901 - 1000 of 1069 matches
Mail list logo
