On 04/11/2012 11:08 AM, Amaury Forgeot d'Arc wrote:
2012/4/11 Ronny Pfannschmidt<ronny.pfannschm...@gmx.de>
hi,
since its kind of troublesome to deal with stdlib vs modified-stdlib,
i'd like to propose an new model for tracking our changes to the stdlib
the unmodified stdlib would be in a branch, say vendor/stdlib,
while our modifications will get inlined in the default branch
that way we get easier merging and easier diffing + we might be able to
supply patches to cpython more easily
the same approach can also be applied to pylib/pytest
so i propose 2 vendor branches for tracking unmodified versions of libs we
use
* vendor/stdlib
* vendor/pytest
and of course the inlining of modified-stdlib
unless there are complaints i would implement the changes in a few days in
a branch
+1. The two directories cause issues in some applications.
Does it make sense to merge lib_pypy as well?
parts of lib_pypy make sense to move (since they map stdlib stuff), but
the parts that are not stdlib should stay
it needs more discussion
in particular pyrepl and that strange distributed thing need to stay
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
