On January 19, 2016 9:37:37 PM CST, Darjus Loktevic wrote:
>Quick background: A little while ago I've added TravisCI integration to
>Jython github mirror. Most recently one of Jython contributors asked
>whether we can integrate the xunit XML output of Jython's regrtest with
>TravisCI. The answer
Hey Ryan,
You're right that Travis supports uploading/deploying to various services.
My wording is really bad there.
For my purposes of exposing the xunit output, i wished that Travis would at
least keep/expose some artifacts itself to save me trouble. Do you know if
that is supported by Travis?
Hi Brett,
>
> Change sys._mercurial
> '
> Once Python is no longer kept in Mercurial, the ``sys._mercurial``
> attribute will need to be removed. An equivalent ``sys._git``
> attribute will be needed to take its place.
>
Would it make sense to change it to something more gene
For backwards compatibility sys._mercurial must probably stay. Maybe it
could be None, so we could write
if sys._mercurial:
...
elif sys._git:
...
else:
# unknown VCS ...
On Wed, Jan 20, 2016 at 12:39 PM, francismb wrote:
> Hi Brett,
> >
> > Change sys._mercurial
> > ''
FWIW sys.subversion has been deprecated in 3.2.1 and removed in 3.3 [0].
In 3.2.1+ and 2.7 it returns ('CPython', '', '').
In theory sys._mercurial is private, so technically we don't have to
go through the same deprecation process, but I see no harm in
deprecating it in 3.6 and then removing it in
Hi,
> Repositories to Migrate
> ===
> While hg.python.org [#h.p.o]_ hosts many repositories, there are only
> five key repositories that should move:
>
> 1. devinabox [#devinabox-repo]_
> 2. benchmarks [#benchmarks-repo]_
> 4. peps [#peps-repo]_
> 5. devguide [#devguide-repo]_
