[issue1827] svnversion_init() doesn't support svn urls in sandbox/trunk

Christian Heimes added the comment: I'm closing this issue as `YAGNI anymore`. -- resolution: -> out of date stage: test needed -> committed/rejected status: open -> closed ___ Python tracker __

[issue1827] svnversion_init() doesn't support svn urls in sandbox/trunk

Mark Lawrence added the comment: Is this ever likely to happen given the switch to Mercurial, or is that a different scenario to this? -- nosy: +BreamoreBoy ___ Python tracker _

[issue1827] svnversion_init() doesn't support svn urls in sandbox/trunk

Daniel Diniz added the comment: I'm setting as 'behavior' because ISTM that a bogus svnversion making Python fail to start is a bug. -- nosy: +ajaksu2 priority: normal -> low stage: -> test needed type: -> behavior versions: +Python 3.1 -Python 3.0 ___

[issue1827] svnversion_init() doesn't support svn urls in sandbox/trunk

Martin v. Löwis added the comment: I fail to see why it is a bug that such URLs are not supported - why can't you develop pep370 in a regular branch? As an RFE, it would certainly possible to support such a case. If either /python/ isn't found, or isn't followed by tags/branches/trunk, I'd set s

[issue1827] svnversion_init() doesn't support svn urls in sandbox/trunk

New submission from Christian Heimes: Python fails to start if headurl points to a svn url under sandbox/. Python/sysmodule.c:svnversion_init() should support those urls or at least fail silently. static const char headurl[] = "$HeadURL: svn+ssh://[EMAIL PROTECTED]/sandbox/trunk/pep370/Python/sy