It is possible to do either of these things, I'm against the first though. Multiple dispatch is not a SymPy project. It's as usable by numpy or IPython as by SymPy.
I'm happy to grant commit rights to anyone who actively develops the project. Ondrej has been futzing with it recently. On Wed, Apr 2, 2014 at 5:02 AM, Jason Moore <moorepa...@gmail.com> wrote: > Is it possible to move the main repository for mutlipledispatch under the > sympy github org and grant the core sympy devs commit rights? > > > Jason > moorepants.info > +01 530-601-9791 > > > On Wed, Apr 2, 2014 at 4:22 AM, Joachim Durchholz <j...@durchholz.org>wrote: > >> Am 02.04.2014 04:10, schrieb Matthew Rocklin: >> >> As a reminder, SymPy currently doesn't depend on any external libraries, >>> so >>> this particular move also represents a policy shift. This potential >>> policy >>> shift follows substantial discussion, notably at >>> https://github.com/sympy/sympy/issues/7339 . There are good reasons for >>> and against external dependencies (I recommend checking out the header of >>> the mentioned issue). >>> I'm now specifically proposing that we depend on multipledispatch which >>> might have other more specific benefits and drawbacks. Even if someone >>> is >>> for dependencies they might not be for this particular dependency. >>> >> >> 1) On multidispatch itself: You can have either modularity or freeness >> from surprises (this has been discussed before - essentially, if you have >> modularity, adding a module with new MD definitions can change dispatch >> decisions for related combinations of types). >> This isn't a problem inside SymPy where we do not expect average users to >> develop subclasses of existing, multi-dispatching SymPy object classes. It >> might become a problem if multi-dispatch is made an independent module. >> >> 2) On external dependencies: My recommendation is that an external >> dependency is okay if and only if those parts of the API that we use are >> stable. That means we need to evaluate how the project's culture handles >> breaking API changes. >> Some minor API changes might be tolerated, or if the project goes to >> great pains to make the current API detectable to SymPy so it can issue the >> right calls. >> >> For MD, I think we should base any decisions on the question what will >> happen if the project is abandoned (project maintainer lose interest, are >> hit by a bus, whatever). >> I'm leaning towards a model that SymPy can use that as an external >> dependency, but be prepared to fork it for its own use as soon as the MD >> project goes in a direction that's unsuitable for SymPy. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sympy" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sympy+unsubscr...@googlegroups.com. >> To post to this group, send email to sympy@googlegroups.com. >> Visit this group at http://groups.google.com/group/sympy. >> To view this discussion on the web visit https://groups.google.com/d/ >> msgid/sympy/533BC8B9.1080002%40durchholz.org. >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sympy+unsubscr...@googlegroups.com. > To post to this group, send email to sympy@googlegroups.com. > Visit this group at http://groups.google.com/group/sympy. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAP7f1AjF6snYpEx_Kc-JPG%2B_Jpan4j-kjCFuOvEJLf%3DQCUkkrg%40mail.gmail.com<https://groups.google.com/d/msgid/sympy/CAP7f1AjF6snYpEx_Kc-JPG%2B_Jpan4j-kjCFuOvEJLf%3DQCUkkrg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAJ8oX-G%3DDHXZZr9wnvL3qLQhG6BgBmKRxybC4OwpFiQPnpaJUQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
