Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Tibor Šimko
    @tiborsimko
    hi, some more tasks before release seem due, I've just sent an email
    Jiri Kuncar
    @jirikuncar
    @tiborsimko Are you going to fix the __version__ import and example?
    Tibor Šimko
    @tiborsimko
    Yes, it's in my release branch... PR soon, I was on open-data in the meantime.
    Tibor Šimko
    @tiborsimko
    Issued #29
    Jiri Kuncar
    @jirikuncar
    PR #29 has been merged
    Tibor Šimko
    @tiborsimko

    WRT dictdiffer vs Dictdiffer, PEP-8 seems to suggest using all lowercase names even for package names:

    Modules should have short, all-lowercase names. Underscores can be used in the module name if it improves readability. Python packages should also have short, all-lowercase names, although the use of underscores is discouraged.

    So I guess I change setup.py back to dictdiffer?

    Jiri Kuncar
    @jirikuncar
    Can you imediatelly push Version bumb to 0.2.0.dev(0|DATETIME) ?
    Tibor Šimko
    @tiborsimko
    Yes, in a minute.
    Jiri Kuncar
    @jirikuncar
    no hurry, just not to forget about it ;)
    Tibor Šimko
    @tiborsimko
    Though maybe 0.1.1.dev20140901 to leave ourselves space to release say a documentation update...
    Jiri Kuncar
    @jirikuncar
    ok
    or we can just keep maint-0.1 branch
    Tibor Šimko
    @tiborsimko
    Yes, though for these "smaller" repositories, I'm not sure whether it is worth it to go for maint/master/next. Until we have bigger changes (OO implementation?) let's keep one branch only.
    Jiri Kuncar
    @jirikuncar
    I’m fine with it
    Tibor Šimko
    @tiborsimko
    Pushed. WRT maint/master branching, let's wait for eventual big changes, like that OO PR.
    Jiri Kuncar
    @jirikuncar
    PRs #31 and #32 should be ready
    Mihai Bivol
    @mihaibivol
    Hey, I saw that the numpy PR is in the 0.6.0 milestone, while the others are in the 0.5.1. Which should be the next release number?
    For the inpsirehep usecase we need to a relase that includes this inveniosoftware/dictdiffer#71
    I could do the release PR myself but I don't know the next version number or if the history after the last release tag should be split into two releases.
    Tibor Šimko
    @tiborsimko
    There does not seem to be any big outstanding issues or feature requests... I guess we could simply head for v0.6.0 (because of the new feature) and skip v0.5.1 altogether, in order to keep the history simple.
    Lars Holm Nielsen
    @lnielsen
    :+1:
    Mihai Bivol
    @mihaibivol
    created #76