#379: Python simfactory branch has a confusing name -------------------------+-------------------------------------------------- Reporter: hinder | Owner: mthomas Type: defect | Status: new Priority: minor | Milestone: ET_2011_11 Component: SimFactory | Version: Resolution: | Keywords: -------------------------+--------------------------------------------------
Comment (by hinder):
I agree with Barry that there is really no need for them to be in the same repository, since they share no history. It just leads to confusion. I still think it is best to move the history of the Python version out into a separate repository. The only development that happens in trunk now is fixing of bugs and updating optionlists (this is rare, but we have done it). This has the advantage that people using the Perl version will still be able to do an svn update to get critical fixes etc without having to go through the pain of switching to a new version just for that, or repointing their svn checkouts to a new branch.
What is the argument against moving the Python version history into a new repository?