#musicbrainz-devel

/

      • alastairp
        interesting comment\
      • 2013-03-12 07125, 2013

      • JonnyJD
        I was kind of suprised (I start using the module for isrcsubmit2)
      • 2013-03-12 07131, 2013

      • alastairp
        right
      • 2013-03-12 07158, 2013

      • alastairp
        I guess it's "you eventually get releases"
      • 2013-03-12 07106, 2013

      • alastairp
        which is why it's get_releases_by_*
      • 2013-03-12 07127, 2013

      • JonnyJD
        Well, it looks like somebody wrote like "what he needs", not what is provided
      • 2013-03-12 07142, 2013

      • JonnyJD
        So from the point of a user, not a dev of the API
      • 2013-03-12 07154, 2013

      • alastairp
        I guess it's because the XML returned from the ws has the <discid> element
      • 2013-03-12 07156, 2013

      • alastairp
        or whatever
      • 2013-03-12 07110, 2013

      • JonnyJD
        A specific user, that is. It does get weird when you DO want the discid request
      • 2013-03-12 07117, 2013

      • alastairp
        hmm, right
      • 2013-03-12 07122, 2013

      • alastairp
        what else does a discid give you?
      • 2013-03-12 07131, 2013

      • JonnyJD
        sectors/toc
      • 2013-03-12 07133, 2013

      • alastairp
        and do you need to inc=releases to make it useful anyway?
      • 2013-03-12 07142, 2013

      • JonnyJD
        no, releases are implied
      • 2013-03-12 07144, 2013

      • alastairp
        ok
      • 2013-03-12 07158, 2013

      • alastairp
        the thing is, I'm not sure a function get_discid() is very useful
      • 2013-03-12 07118, 2013

      • alastairp
        or maybe we need a get_discid, and a wrapper, get_releases_by_discid that returns just a release list
      • 2013-03-12 07103, 2013

      • alastairp
        I want to do an api rewrite for 0.5
      • 2013-03-12 07113, 2013

      • alastairp
        lots of things I want to change/fix
      • 2013-03-12 07147, 2013

      • JonnyJD
        well, I also need get_releases in terms of actually getting releases, though
      • 2013-03-12 07134, 2013

      • alastairp
        but you can just use get_release_by_id for that?
      • 2013-03-12 07137, 2013

      • JonnyJD
        The point is, I access the "release_list" with ["disc"]["release-list"]
      • 2013-03-12 07111, 2013

      • JonnyJD
        yes, from the technical point it works, after I found out that this gives me the discid, not a release-list
      • 2013-03-12 07126, 2013

      • JonnyJD
        So this is only a usage issue
      • 2013-03-12 07134, 2013

      • alastairp
        ok, and the function name made you think it should give you a release-list?
      • 2013-03-12 07141, 2013

      • JonnyJD
        A relevant one though, since we have no wrapper, but expose the dicts directly
      • 2013-03-12 07146, 2013

      • JonnyJD
        Yes.
      • 2013-03-12 07156, 2013

      • alastairp
        if that's the case then my preference would be to have 2 methods ^^\
      • 2013-03-12 07114, 2013

      • alastairp
        get_discid will give a <discid>, get_releases will parse that and just return the list
      • 2013-03-12 07123, 2013

      • JonnyJD
        That would work.
      • 2013-03-12 07117, 2013

      • JonnyJD
        Like I said, I am actually interested in get_releases, it's just that the usage is not at all straightforward.
      • 2013-03-12 07137, 2013

      • JonnyJD
        Do you open a ticket for 0.5 (api change)?
      • 2013-03-12 07145, 2013

      • JonnyJD
        Or should I
      • 2013-03-12 07108, 2013

      • alastairp
        if no one else is using it, I'm happy to break api on the next release
      • 2013-03-12 07111, 2013

      • alastairp
        file against 0.3\
      • 2013-03-12 07122, 2013

      • alastairp
        check if beets or headphones use it
      • 2013-03-12 07126, 2013

      • JonnyJD
        Well, there is samsyo
      • 2013-03-12 07136, 2013

      • alastairp
        sampsyo: ?? :)
      • 2013-03-12 07143, 2013

      • JonnyJD
        asampson
      • 2013-03-12 07148, 2013

      • JonnyJD
        beets dev
      • 2013-03-12 07125, 2013

      • JonnyJD
        Mineo has a isrcsubmit variant that uses the function, but I guess that is no big deal
      • 2013-03-12 07155, 2013

      • alastairp
        nothing in beets
      • 2013-03-12 07138, 2013

      • alastairp
        headphones uses _by_discid
      • 2013-03-12 07153, 2013

      • alastairp
        no, wait
      • 2013-03-12 07104, 2013

      • alastairp
        it just has its own copy of mbngs
      • 2013-03-12 07141, 2013

      • JonnyJD
        Well, then they can decice if they update it or not.
      • 2013-03-12 07119, 2013

      • alastairp
        so I'm happy to put it in the next release, or wait until the api break release
      • 2013-03-12 07129, 2013

      • alastairp
        fingers crossed next release will be within in a month
      • 2013-03-12 07128, 2013

      • JonnyJD
        For isrcsubmit2 I could wrap it (test which dict I get). So it's up to you when to include the API change.
      • 2013-03-12 07135, 2013

      • alastairp
        k
      • 2013-03-12 07155, 2013

      • alastairp
        can you remember who the debian maintainer is?
      • 2013-03-12 07101, 2013

      • alastairp
        I have a bunch of emails from him
      • 2013-03-12 07104, 2013

      • alastairp
        but can't remember his name
      • 2013-03-12 07109, 2013

      • JonnyJD
        The earlier it is, the earlier people can adapt and/or start using pymbngs with the new API
      • 2013-03-12 07115, 2013

      • JonnyJD
        nope
      • 2013-03-12 07136, 2013

      • JonnyJD
      • 2013-03-12 07155, 2013

      • JonnyJD
        For debian you have to check if you want to include it in wheezy or not
      • 2013-03-12 07105, 2013

      • alastairp
        oh, it was a netbsd guy
      • 2013-03-12 07108, 2013

      • alastairp
        just replied to him
      • 2013-03-12 07140, 2013

      • JonnyJD
        Currently the 0.2 API will be in Debian wheezy. (stable)
      • 2013-03-12 07158, 2013

      • alastairp
        when's wheezy planning to go stable?
      • 2013-03-12 07113, 2013

      • JonnyJD
        No real plan, but they release RC1 in february
      • 2013-03-12 07122, 2013

      • JonnyJD
        *released
      • 2013-03-12 07150, 2013

      • JonnyJD
        so it's like "anytime now"
      • 2013-03-12 07154, 2013

      • alastairp
        right
      • 2013-03-12 07104, 2013

      • alastairp
        so 0.3 definitely, probably not 0.4
      • 2013-03-12 07108, 2013

      • alastairp
        well, definitely
      • 2013-03-12 07110, 2013

      • alastairp
        hopefully
      • 2013-03-12 07129, 2013

      • JonnyJD
      • 2013-03-12 07102, 2013

      • alastairp
        huh, right
      • 2013-03-12 07109, 2013

      • alastairp
        let me email Jonas
      • 2013-03-12 07119, 2013

      • adhawkins joined the channel
      • 2013-03-12 07147, 2013

      • alastairp
        he says it's fixed -- is it?
      • 2013-03-12 07159, 2013

      • alastairp
        or does your patch fix it?
      • 2013-03-12 07112, 2013

      • JonnyJD
        that is the fix I called "hiding fix"
      • 2013-03-12 07134, 2013

      • alastairp
        I can't find the debdiff
      • 2013-03-12 07137, 2013

      • JonnyJD
        I think, checking atm
      • 2013-03-12 07106, 2013

      • JonnyJD
      • 2013-03-12 07157, 2013

      • JonnyJD
        The error is gone, but the includes don't work right, unless given as explicit keyword
      • 2013-03-12 07116, 2013

      • alastairp
        OK
      • 2013-03-12 07135, 2013

      • alastairp
        I'm tempted to spin a 0.4 in the next few days then with your current fix, no api change
      • 2013-03-12 07157, 2013

      • JonnyJD
        Don't rush things though.
      • 2013-03-12 07125, 2013

      • JonnyJD
        That problem persists for a year already and nobody noticed. So we have enough time for additional review.
      • 2013-03-12 07151, 2013

      • alastairp
        I'll email Jonas, see what his status is - if he just replied to the morituri bug, or is now a maintainer
      • 2013-03-12 07124, 2013

      • alastairp
        do you know if packages.debian.org gives rdepends output? (I can see depends)
      • 2013-03-12 07149, 2013

      • JonnyJD
        No, I don't know.
      • 2013-03-12 07142, 2013

      • alastairp
        I /suppose/ I could install debian in a vm :-P
      • 2013-03-12 07122, 2013

      • JonnyJD
        On Arch Linux only "beets" needs python-musicbrainzngs atm. Morituri doesn't (morituri 0.2.0)
      • 2013-03-12 07148, 2013

      • alastairp
        ok
      • 2013-03-12 07154, 2013

      • alastairp
        yeah, same in the latest ubuntu
      • 2013-03-12 07135, 2013

      • JonnyJD
        I also don't have an unstable or testing debian VM atm
      • 2013-03-12 07125, 2013

      • alastairp
        installing testing now
      • 2013-03-12 07157, 2013

      • Ben\Sput joined the channel
      • 2013-03-12 07129, 2013

      • alastairp
        heh, mirrors on peer'd networks are fast :)
      • 2013-03-12 07132, 2013

      • navap
        I'm getting a start up error: "encode_base64url" is not exported by the MIME::Base64 module
      • 2013-03-12 07140, 2013

      • navap
        Any ideas?
      • 2013-03-12 07158, 2013

      • warp
        navap: yes
      • 2013-03-12 07132, 2013

      • warp
      • 2013-03-12 07113, 2013

      • hawke_1 joined the channel
      • 2013-03-12 07149, 2013

      • navap
        Awesome, thanks
      • 2013-03-12 07135, 2013

      • hawke joined the channel
      • 2013-03-12 07102, 2013

      • alastairp
        JonnyJD: ok, finally got experimental merged
      • 2013-03-12 07110, 2013

      • alastairp
        morituri is an rdepends
      • 2013-03-12 07119, 2013

      • alastairp
        0.2.0-1
      • 2013-03-12 07125, 2013

      • alastairp
        only that and beets,though
      • 2013-03-12 07109, 2013

      • alastairp
        squeeze and sid/wheezy are still at 0.1.2
      • 2013-03-12 07117, 2013

      • alastairp
        experiemental is 0.2
      • 2013-03-12 07158, 2013

      • JonnyJD
        are you sure? http://packages.qa.debian.org/m/musicbrainzngs.ht… says 0.2-1 is in testing
      • 2013-03-12 07129, 2013

      • JonnyJD
        experimental is 0.2-1.1, according do that
      • 2013-03-12 07132, 2013

      • alastairp
        unless this mirror hasn't updated yet, apt-cache policy says sid has 0.1.2-2
      • 2013-03-12 07145, 2013

      • alastairp
        oh
      • 2013-03-12 07149, 2013

      • alastairp
        I mean morituri
      • 2013-03-12 07152, 2013

      • alastairp
        not pymb
      • 2013-03-12 07159, 2013

      • JonnyJD
        ah, k
      • 2013-03-12 07157, 2013

      • JonnyJD
        Yes, that is because of wheezy freeze, I guess. Libdiscid also isn't progressing to unstable.
      • 2013-03-12 07142, 2013

      • alastairp
        right, yeah
      • 2013-03-12 07148, 2013

      • JonnyJD
        So that means beets and morituri need to be patched or updated when pymbngs gets into debian etc. with a different (backwards incompatible) api.
      • 2013-03-12 07129, 2013

      • alastairp
        yes
      • 2013-03-12 07152, 2013

      • alastairp
        we can submit an issue to them before the release saying the api is changing
      • 2013-03-12 07117, 2013

      • alastairp
        I may consider bumping the major version so make it clear there's a break
      • 2013-03-12 07121, 2013

      • JonnyJD
        Yes, that is a possibility. semver.org says 0.x API isn't supposed to be stable, but pymbngs is already out for some time.
      • 2013-03-12 07134, 2013

      • JonnyJD
        Libdiscid is also stable in 0.x releases ;-)
      • 2013-03-12 07145, 2013

      • JonnyJD
        That also means you are supposed to keep making bugfixes for the 0.x branch then.
      • 2013-03-12 07105, 2013

      • alastairp
        that's exactly what I was thinking of
      • 2013-03-12 07116, 2013

      • alastairp
        "technically", breaking an api on 0.x is fine :)
      • 2013-03-12 07128, 2013

      • JonnyJD
        I guess I would have lots of angry mails when I would introduce a backwards incompatibe change in Libdiscid after 7 years :-D
      • 2013-03-12 07104, 2013

      • JonnyJD
        So much for "technically". You have to talk about that with the beets and morituri devs, I guess.
      • 2013-03-12 07113, 2013

      • JonnyJD
        For isrcsubmit I kept working on isrcsubmit1, because pymbngs isn't supposed to be stable anyways ;-)
      • 2013-03-12 07122, 2013

      • alastairp
        sure
      • 2013-03-12 07133, 2013

      • Freso_laptop joined the channel
      • 2013-03-12 07145, 2013

      • teuf_ joined the channel
      • 2013-03-12 07147, 2013

      • Ben\Sput has left the channel
      • 2013-03-12 07100, 2013

      • CatCat joined the channel
      • 2013-03-12 07120, 2013

      • alastairp
        heh, got a nice email from the debian packager
      • 2013-03-12 07134, 2013

      • alastairp
        saying "how nice that you email the package maintainers after you make a release"
      • 2013-03-12 07154, 2013

      • alastairp
        it turns out the easy way to do it is to just wait for their magic system to realise there's a new version on pypi
      • 2013-03-12 07130, 2013

      • hawke_1
        blah, I hate aliases. is “サンセット・フライト” Japanese, or is it English (in katakana script)?
      • 2013-03-12 07142, 2013

      • hawke_1
        kinda wrong channel but whatever
      • 2013-03-12 07134, 2013

      • JonnyJD
        alastairp: yes, they have this "watch" file. So after 1-2 days it turns up in the dashboard and possibly they also get a mail. When you send a mail you can tell them about important things though.
      • 2013-03-12 07116, 2013

      • JonnyJD
        So I also send mails/open update requests for "important releases".
      • 2013-03-12 07136, 2013

      • alastairp
        right
      • 2013-03-12 07150, 2013

      • alastairp
        I've sub'd to the package, anyway, so I can see any updates that happen there
      • 2013-03-12 07149, 2013

      • CatCat
        hawke: try http://nihongo.j-talk.com/ and see if the katakana is anything remotly soundign logic in english http://nihongo.j-talk.com/
      • 2013-03-12 07129, 2013

      • hawke_1
        CatCat: →#musicbrainz
      • 2013-03-12 07130, 2013

      • CatCat
        sunset fright?
      • 2013-03-12 07138, 2013

      • CatCat
        what?
      • 2013-03-12 07145, 2013

      • CatCat
        but you *Asked* here
      • 2013-03-12 07103, 2013

      • hawke_1
        yeah I re-asked in #musicbrainz
      • 2013-03-12 07105, 2013

      • hawke_1
        :-)