aixtools added the comment: On 6/12/2016 11:41 AM, Martin Panter wrote: > . > Michael, how are you supposed to apply your latest patch? I have Gnu Patch > 2.7.5, but even in the best case it doesn’t find the files to patch: > > $ patch -p1 -n < python.Lib.ctypes.160608.patch > can't find file to patch at input line 2 > The text leading up to this was: > -------------------------- > |diff -r Python-2.7.11/Lib/ctypes/__init__.py > python-2.7.11.5/Lib/ctypes/__init__.py > -------------------------- I must have forgotten the u (-r rather than -ru) (read mistyped, as I "always" use the -u option) > Perhaps can you make a “unified” diff (-u option) like you did in your > previous patches? Whatever you did with Python3.issue26439.160511.patch > seemed to work best. Will redo all of them in about 24 hours. > Also, since your patches add new functionality (the automatic archive member > detection), they will have to be for Python 3, not 2.
Well, let me know what needs to be deleted - I see the member detection as the equivalent of reading the output of "ldconfig -p" to search for where an archive might be, or compareable with the gcc command (forgot the options) to say where it is looking. Not going into Python2 misses the whole point from my perspective. Unfortunate (for my perspective) is that noone else is saying anything one way or the other. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26439> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
