[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Changes by Stefan Krah : -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed versions: +Python 2.7, Python 3.3, Python 3.4 -Python 3.1, Python 3.2 ___ Python tracker

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Roundup Robot added the comment: New changeset 6df456f8fc6d by Stefan Krah in branch '3.3': Issue #7353: Remove references to Include/intobject.h in the C-porting howto. http://hg.python.org/cpython/rev/6df456f8fc6d -- nosy: +python-dev ___ Python tra

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Christian Heimes added the comment: Go ahead! The intobject header file used to make porting to Python 3 easier. Nowadays it's no longer required. -- ___ Python tracker ___

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Stefan Krah added the comment: I tend to agree with the argument that the removal of intobject.h was a good thing, since it avoids subtle errors. Probably no one wants to reinstate intobject.h at this point, so unless there are objections, I'll update the docs in a couple of days. -- ke

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Ramchandra Apte added the comment: Bump... is this still valid? -- nosy: +ramchandra.apte ___ Python tracker ___ ___ Python-bugs-list m

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Changes by Éric Araujo : -- assignee: -> d...@python nosy: +d...@python ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Changes by Skip Montanaro : -- nosy: -skip.montanaro ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Iustin Pop added the comment: Hi, Might I suggest that, whatever the outcome of the re-adding intobject.h discussion, the documentation is updated? I think I'm not the only module author which spent time trying to understand why the 3.1 documentation refers to non-existent header before finally

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Marc-Andre Lemburg added the comment: Eric pointed me to this ticket after having raised the question on python-dev: http://www.mail-archive.com/python-...@python.org/msg43841.html I think the discussion should be continued there instead of on this ticket. Just for completeness, I'm copying my

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Eric Smith added the comment: MvL made this comment in http://www.mail-archive.com/python-...@python.org/msg43844.html I'm copying it here so it doesn't get lost and because I think he makes a good point that many people would miss (at least I didn't think of it). --

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Guido van Rossum added the comment: I don't think it would hurt to put it back, would it? I think the "remove this in 3.1" note was made when we expected 3.1 to be happening 1.5 years after 3.0 rather than a few months. -- nosy: +gvanrossum ___ Py

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Mark Dickinson added the comment: [Benjamin] >I wish intobject.h hadn't been removed so soon. Yes; I'm sorry about that. > I'm not really sure how a file of #defines could suffer bitrot. Good point. Me neither. -- ___ Python tracker

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Benjamin Peterson added the comment: Hmm, I wish intobject.h hadn't been removed so soon. I'm not really sure how a file of #defines could suffer bitrot. This point is probably moot, though because there's little point in having its presence skip a version. I suppose sticking it in Tools or even

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Changes by R. David Murray : -- nosy: -r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

R. David Murray added the comment: You didn't. Doc bugs are automatically assigned to Georg by the tracker. -- nosy: +r.david.murray priority: -> normal stage: -> needs patch title: Why was Include/intobject.h removed in 3.1? -> cporting docs recommend using Include/intobject.h, whi