#readthedocs

/

      • primehaxor has quit
      • jMyles joined the channel
      • orbisvicis has quit
      • f10w has quit
      • f10w joined the channel
      • primehaxor joined the channel
      • primehaxor has quit
      • untitaker joined the channel
      • kushal has quit
      • kushal joined the channel
      • kushal has quit
      • kushal joined the channel
      • ojii joined the channel
      • takotuesday joined the channel
      • takotuesday has quit
      • takotuesday joined the channel
      • takotuesday has quit
      • wlach joined the channel
      • ojii has quit
      • agj
        nedbat: we don't do a great job explaining it, the default settting just points to 'latest'
      • nedbat
        agj: but there's the build named "default" and the build that has "default" checked on it.
      • ericholscher
        nedbat: latest is an alias that works across all VCS types and can point at different things
      • its basically the thing we need to build in order to build something for everyone on first import
      • and it defaults to the VCS "default" branch
      • its generally also the version we always expect to exist on any repo as well
      • nedbat
        ericholscher: I have four active versions: https://readthedocs.org/projects/coverage/versi...
      • ericholscher
        and the default version we redirect / to
      • nedbat
        ericholscher: I entered "coverage-3.7.1" in the "default version" setting on the advanced settings page, but it doesn't seem to affect what is marked as default on the versions page.
      • RTDGitHubBot joined the channel
      • NOTICE: [readthedocs.org] ericholscher pushed 1 new commit to master: http://git.io/FmEA
      • NOTICE: readthedocs.org/master c5f696e Eric Holscher: Clarify stable language
      • RTDGitHubBot has left the channel
      • though it does change what is shown at /
      • ericholscher
        yea, those are different settings -- there is a "latest" version setting too
      • the UI around it is a little bit confusing :)
      • we're working on fixing it
      • (eg. with that fancy new versions page)
      • nedbat: https://www.dropbox.com/s/f1q6jei87ru94a3/Scree... on the advanced settings page
      • nedbat
        ericholscher: I think i know enough to make it work for my needs.
      • ericholscher
        nedbat: if your version names weren't prefixed, they would auto-update a stable branch that you could default to, and it would mostly just work
      • guessing distlib can't parse the tag string, so we don't create them
      • nedbat
        I see.
      • I thought about removing the prefix, to get it out of the URL also
      • ericholscher: and stable knows not to take 4.0a4 as stable, because it's alpha?
      • ericholscher
        hmm, perhaps not
      • iirc there's a bug about that
      • :(
      • we need to upgrade to whatever the new version lib is in python, and iirc that will fix it
      • fgs
        anyne from rtd that can answer my question from a couple of days back?
      • ericholscher
        fgs: which was?
      • sorry, don't have that much scrollback
      • fgs: also, feel free to file a GH issue for that kind of stuff so it doesn't get lost -- IRC has a way of disappearing
      • fgs
        ericholscher: some rst files are generated as part of the build project
      • IIUC there is no way to push the files so I need to point it to another repo/branch where the generated files are available.
      • That could work for the time being but the reference to the repo/branch will be off
      • ericholscher
        sounds like you want a git submodule
      • fgs
        So my 3 Q's: 1. is there any ETA to be able to push things? 2. Is there any alternative? 3. Is there any way to change the references to github so it's pulled from one place but shows the right branch?
      • ericholscher
        but generaly, not really
      • i'd be curious what the use case for this is
      • what are the generated files?
      • fgs
        rst files and images included in those rst files
      • ericholscher
        1: "soon" :) 2: git submodule is probably the sanest answer 3: no
      • fgs
        T_T
      • Is there any way to help so that "soon" becomes "sooner"? :)
      • ericholscher
        if you contribute it
      • otherwise its on our list, but not a big priority
      • fgs
        ok
      • not much time on my hands but I will see what I can do
      • whit537 joined the channel
      • takotuesday joined the channel
      • whit537 has quit
      • juliaelman has quit
      • henrikbjorn has quit
      • bret joined the channel
      • henrikbjorn joined the channel
      • juliaelman joined the channel
      • takotuesday has quit
      • ZenWraithBot1 has quit
      • ZenWraithBot joined the channel
      • c74d3 is now known as c74d
      • takotuesday joined the channel
      • takotuesday has quit