On 03/09/2011 01:15 AM, Stefan Behnel wrote:
I can confirm that the Cython project was as surprised of the
PyCapsule change in Python 3.2 as (I guess) most other users,
I was a bit surprised by it too, and I wrote the Capsule object. (Well,
hacked up CObject to give it a new API.)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/03/11 22:50, Guido van Rossum wrote:
I propose we try to find an embedded blogger who participates in
python-dev but is focused on making regular blog posts about the
interesting tidbits. There's no requirement to be complete (which I
think
On Mar 16, 2011, at 11:07 AM, Jesus Cea wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/03/11 22:50, Guido van Rossum wrote:
I propose we try to find an embedded blogger who participates in
python-dev but is focused on making regular blog posts about the
interesting tidbits.
On Mon, Mar 14, 2011 at 19:22, Reid Kleckner reid.kleck...@gmail.com wrote:
I don't know how your code works, but handling either type from C
seems very straightforward to me. You can simply use #ifdef
Py_COBJECT_H to see if the cobject.h header was pulled into Python.h.
Similarly for
On 3/14/11 5:30 PM, Lennart Regebro wrote:
Many projects, not only the Zope Toolkit needs to support a lot of
versions. The Zope component architecture currently supports 2.4, 2.5
and 2.6 and is expected to work on 2.7. I don't know if 2.4 or 2.5 can
be dropped, but it definitely will be
On Wed, Mar 9, 2011 at 01:15, Stefan Behnel stefan...@behnel.de wrote:
I can confirm that the Cython project was as surprised of the PyCapsule
change in Python 3.2 as (I guess) most other users, and I would claim that
we are a project with one of the highest probabilities of being impacted by
On Mon, Mar 14, 2011 at 6:30 PM, Lennart Regebro rege...@gmail.com wrote:
On Wed, Mar 9, 2011 at 01:15, Stefan Behnel stefan...@behnel.de wrote:
I can confirm that the Cython project was as surprised of the PyCapsule
change in Python 3.2 as (I guess) most other users, and I would claim that
we
On Mar 11, 2011, at 7:12 PM, Paul Moore wrote:
On 11 March 2011 23:24, Guido van Rossum gu...@python.org wrote:
I'm interested in the task and I guess I'll follow-up with Doug Hellman. I
don't follow -ideas close enough to summarize it, but I'd contribute to a
-dev blog.
Awesome! (And we
On Wed, 09 Mar 2011 07:15:07 +0100
Stefan Behnel stefan...@behnel.de wrote:
Actually, why not put up a web page of upcoming changes somewhere, that
lists major decisions with user impact that were taken on python-dev?
Including a link to the relevant discussion and decision. Often enough,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2011 03:24 PM, Antoine Pitrou wrote:
On Wed, 09 Mar 2011 07:15:07 +0100
Stefan Behnel stefan...@behnel.de wrote:
Actually, why not put up a web page of upcoming changes somewhere, that
lists major decisions with user impact that were
On Wed, Mar 9, 2011 at 3:40 PM, Doug Hellmann doug.hellm...@gmail.com wrote:
On Mar 9, 2011, at 9:50 AM, Tim Lesher wrote:
On Wed, Mar 9, 2011 at 01:15, Stefan Behnel stefan...@behnel.de wrote:
Actually, why not put up a web page of upcoming changes somewhere, that
lists major decisions with
On Fri, 11 Mar 2011 15:53:03 -0500
Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2011 03:24 PM, Antoine Pitrou wrote:
On Wed, 09 Mar 2011 07:15:07 +0100
Stefan Behnel stefan...@behnel.de wrote:
Actually, why not put up a web page of
On Wed, 9 Mar 2011 15:40:56 -0500
Doug Hellmann doug.hellm...@gmail.com wrote:
The original request from the board was for the communications team to write
the messages, but I think it is more appropriate for the people doing the
work to talk about it. [...]
I asked Michael to add this
On Mar 11, 2011 4:52 PM, Guido van Rossum gu...@python.org wrote:
On Wed, Mar 9, 2011 at 3:40 PM, Doug Hellmann doug.hellm...@gmail.com
wrote:
On Mar 9, 2011, at 9:50 AM, Tim Lesher wrote:
On Wed, Mar 9, 2011 at 01:15, Stefan Behnel stefan...@behnel.de
wrote:
Actually, why not put up a
On Fri, 11 Mar 2011 22:56:49 +0100
Antoine Pitrou solip...@pitrou.net wrote:
On Fri, 11 Mar 2011 15:53:03 -0500
Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2011 03:24 PM, Antoine Pitrou wrote:
On Wed, 09 Mar 2011 07:15:07 +0100
On Fri, Mar 11, 2011 at 5:05 PM, Brian Curtin brian.cur...@gmail.com wrote:
On Mar 11, 2011 4:52 PM, Guido van Rossum gu...@python.org wrote:
On Wed, Mar 9, 2011 at 3:40 PM, Doug Hellmann doug.hellm...@gmail.com
wrote:
On Mar 9, 2011, at 9:50 AM, Tim Lesher wrote:
On Wed, Mar 9, 2011
On 11 March 2011 23:24, Guido van Rossum gu...@python.org wrote:
I'm interested in the task and I guess I'll follow-up with Doug Hellman. I
don't follow -ideas close enough to summarize it, but I'd contribute to a
-dev blog.
Awesome! (And we don't need to stop at one blogger. Many hands make
On Wed, Mar 9, 2011 at 1:15 AM, Stefan Behnel stefan...@behnel.de wrote:
A publicly visible list of those decisions would
a) make it easier for non-core developers to follow important changes on
python-dev
b) allow potentially impacted people to bring up their POV more quickly,
e.g. during
On Wed, Mar 9, 2011 at 01:15, Stefan Behnel stefan...@behnel.de wrote:
Actually, why not put up a web page of upcoming changes somewhere, that
lists major decisions with user impact that were taken on python-dev?
Including a link to the relevant discussion and decision. Often enough,
decisions
On Wed, Mar 9, 2011 at 1:15 AM, Stefan Behnel stefan...@behnel.de wrote:
Martin v. Löwis, 08.03.2011 23:47:
I think everything here is as it should be. People who really cared
about forwards compatibility could have known, but factually, most
people don't care enough. Those then learn for the
Actually, why not put up a web page of upcoming changes somewhere, that
lists major decisions with user impact that were taken on python-dev?
I think what's new serves this purpose properly.
Usually, every time I commit a new feature, I update the what's new
file as well.
In fact we already
On Mar 9, 2011, at 9:50 AM, Tim Lesher wrote:
On Wed, Mar 9, 2011 at 01:15, Stefan Behnel stefan...@behnel.de wrote:
Actually, why not put up a web page of upcoming changes somewhere, that
lists major decisions with user impact that were taken on python-dev?
Including a link to the relevant
On Wed, 9 Mar 2011 19:42:36 +0100
Giampaolo Rodolà g.rod...@gmail.com wrote:
Actually, why not put up a web page of upcoming changes somewhere, that
lists major decisions with user impact that were taken on python-dev?
I think what's new serves this purpose properly.
Usually, every time I
On 3/9/2011 4:14 PM, Antoine Pitrou wrote:
On Wed, 9 Mar 2011 19:42:36 +0100
Perhaps the part of the what's new document which deals with porting
issues and compatibility breakage would need more highlighting?
That could go at the tops.
Deletions in 3.3
...
Planned deletions in future
On 3/9/2011 9:50 AM, Tim Lesher wrote:
We used to do biweekly-ish Python-Dev summaries for this reason.
They were, is a sense, too detailed, complete, and voluminous.
In whatever format, terser announcement of just things others really
need to know - like decisions that affect them, would
Martin v. Löwis, 08.03.2011 23:47:
I think everything here is as it should be. People who really cared
about forwards compatibility could have known, but factually, most
people don't care enough. Those then learn for the first time that
some feature was deprecated after it is actually removed.
26 matches
Mail list logo
