On Feb 13, 2010, at 1:31 AM, Martin v. Löwis wrote: >>> On Fri, Feb 12, 2010 at 11:17, "Martin v. Löwis" <mar...@v.loewis.de> wrote: >>>> IMO, it is realistic to predict that this will not actually happen. If >>>> we can agree to give up the 2to3 sandbox, we should incorporate >>>> find_pattern into the tree, and perhaps test.py as well. >>> I vote on giving up the 2to3 sandbox. >> >> Besides, if we're using hg, it should make it much easier for someone >> else to branch that part of the stdlib > > Actually - no: hg doesn't support branching of parts of a repository. > You would need to branch all of Python. Then, there wouldn't be a > straight-forward place to setup.py and any other top-level files > (although you could hack them into Lib, and work with a distutils manifest).
Does hg support an equivalent of 'bzr split'? % bzr split --help Purpose: Split a subdirectory of a tree into a separate tree. Usage: bzr split TREE Options: --usage Show usage message and options. -v, --verbose Display more information. -q, --quiet Only display errors and warnings. -h, --help Show help message. Description: This command will produce a target tree in a format that supports rich roots, like 'rich-root' or 'rich-root-pack'. These formats cannot be converted into earlier formats like 'dirstate-tags'. The TREE argument should be a subdirectory of a working tree. That subdirectory will be converted into an independent tree, with its own branch. Commits in the top-level tree will not apply to the new subtree. See also: join -Barry _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
