[issue7718] Build shared libpythonX.Y.so on IRIX

Berker Peksag added the comment: According to the python-dev discussion, Irix is not supported anymore: https://mail.python.org/pipermail/python-dev/2009-February/086111.html -- nosy: +berker.peksag resolution: -> out of date stage: -> committed/rejected status: open -> closed __

[issue7718] Build shared libpythonX.Y.so on IRIX

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue7718] Build shared libpythonX.Y.so on IRIX

Mark Lawrence added the comment: Stuart has been asked to sign the paperwork on #7717. -- nosy: +BreamoreBoy ___ Python tracker ___ __

[issue7718] Build shared libpythonX.Y.so on IRIX

Brian Curtin added the comment: I'll reopen this for now, no need for duplicate issues. http://www.python.org/psf/contrib/ has the relevant contributor agreement that should be signed. -- resolution: rejected -> status: closed -> open ___ Python t

[issue7718] Build shared libpythonX.Y.so on IRIX

Fabian Groffen added the comment: Is it necessary to file a new bug for the same issue, or can we reopen from here? With Stuart in the loop it looks to me the raised issues are dealt with? -- ___ Python tracker _

[issue7718] Build shared libpythonX.Y.so on IRIX

Stuart Shelton added the comment: I've no objection to signing the relevant paperwork if that's what's needed to get this committed - if someone could point me in the direction of what I needed to do in order to do so? -- nosy: +srcshelton ___ Pyth

[issue7718] Build shared libpythonX.Y.so on IRIX

Fabian Groffen added the comment: I've asked Stuart to sign up and comment on this bug to get his opinion. Sorry. -- ___ Python tracker ___ _

[issue7718] Build shared libpythonX.Y.so on IRIX

Changes by Martin v. Löwis : -- resolution: postponed -> rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7718] Build shared libpythonX.Y.so on IRIX

Martin v. Löwis added the comment: I think the patch in its current form is then, unfortunately, not acceptable - unless Stuart Shelton actually signs a contributor agreement. I don't know what makes you believe that he actually meant to contribute the code to Python, but I just don't want to

[issue7718] Build shared libpythonX.Y.so on IRIX

Fabian Groffen added the comment: I think so. From my experience he's mainly not willing to sign up to each and every bugtracking system, which I fully understand. Do you guys need signed contracts for each and every (even single line) patch? Is it better to report the problem and how it ca

[issue7718] Build shared libpythonX.Y.so on IRIX

Brian Curtin added the comment: #7717 also contains code "on behalf of" other people. -- nosy: +brian.curtin priority: -> normal type: -> feature request ___ Python tracker ___

[issue7718] Build shared libpythonX.Y.so on IRIX

Martin v. Löwis added the comment: I'm worried about this "on behalf of" contribution. Does Stuart Shelton actually approve this contribution? Would he be willing to sign a contributor agreement? -- nosy: +loewis ___ Python tracker

[issue7718] Build shared libpythonX.Y.so on IRIX

New submission from Fabian Groffen : Create a libpythonX.Y.so library on IRIX. Patch on behalf of Stuart Shelton. -- components: Build files: python-2.6-irix-libpython2.6.patch keywords: patch messages: 97897 nosy: grobian severity: normal status: open title: Build shared libpythonX.Y.s