Benny Siegert bsieg...@gmail.com added the comment:
Hmm, I thought I was making an argument _for_ applying the patch. As I see it,
these are benefits of merging the patch:
1. Being able to compile an unmodified upstream Python on MirBSD.
2. The patches in pkgsrc become smaller.
3. Future
Martin v. Löwis mar...@v.loewis.de added the comment:
You said I can maintain the patch for future releases. This sounds like a
reasonable solution: you keep maintaining the patch; if you want python.org to
link to your patch, we can certainly arrange that. By the no minority
platforms
Benny Siegert bsieg...@gmail.com added the comment:
I agree that the patch is quite small. I am regularly building new Python
versions (using pkgsrc) so I can maintain the patch for future releases.
--
___
Python tracker rep...@bugs.python.org
Martin v. Löwis mar...@v.loewis.de added the comment:
Ok, closing this as won't fix, them.
--
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12976
Charles-François Natali neolo...@free.fr added the comment:
Hello Benny,
As requested, here is the full patch for MirBSD support. The diff was taken
against version 2.7.2. It is really quite easy, you just need to handle
MirBSD like OpenBSD.
With this patch, I can successfully compile and
Benny Siegert bsieg...@gmail.com added the comment:
As requested, here is the full patch for MirBSD support. The diff was taken
against version 2.7.2. It is really quite easy, you just need to handle MirBSD
like OpenBSD.
With this patch, I can successfully compile and run Python on MirBSD.
Changes by Benny Siegert bsieg...@gmail.com:
Removed file: http://bugs.python.org/file23153/patch-az
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12976
___
