Ferran, Welcome to SymPy! I'll answer some of the questions that I know, other will chime in for the rest.
> We have read that sympy supports python 2 and 3. How does this affect the development process? You should write your code for Python 3.5 and when you submit a pull request our continuous integration service will run the tests on other versions of Python. You'll then need to fix any errors. We have a compatibility module to help with many of the common needs for dual support of Python 2 and 3. You can also test your code locally on both versions. I recommend using conda to switch between Python 2 and 3 environments. > We have read that sympy supports python 2 and 3. How does this affect the development process? We highly recommend smaller atomic pull requests. You are much more likely to get reviewed in a timely fashion if you submit small PRs. > Any further help or comments are also welcome :) I recommend starting here: https://github.com/sympy/sympy/wiki/introduction-to-contributing. And don't be shy about asking questions here or on the gitter channel. Jason moorepants.info +01 530-601-9791 On Fri, Sep 16, 2016 at 5:57 AM, Ferran Pujol Camins < ferranpujolcam...@gmail.com> wrote: > Hello, > I represent a group of 6 students from the maths school (FME) of the > Universitat Politècnica de Catalunya. > In one of our courses we have been assigned to the task of implementing > QEPCAD in python using sympy. Our goal is to develop a module that can be > merged into sympy. > > We have just started, so our knowledge of QEPCAD and sympy is limited, but > we expect to success in our goal by the end of the semester. We would > really appreciate some help to get started. > > - We have seen that QEPCAD was in a GSOC proposal. AFAIK, the proposal > was not accepted or the project didn't get finished. Is there something > more about it we should know? Maybe some work is already done? > - We have read that sympy supports python 2 and 3. How does this > affect the development process? > - How does QEPCAD fit into the existing modules ecosystem? Should our > work go into its own module or inside an already existing one? > - What's the merging policy for a new module? One monolithic PR with > functional code? Or several small PR that might not be usable yet? > - Any further help or comments are also welcome :) > > > Best regards, Ferran. > > -- > 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 https://groups.google.com/group/sympy. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/sympy/2a351f04-26bf-405a-a8bc-76eb6025f5eb%40googlegroups.com > <https://groups.google.com/d/msgid/sympy/2a351f04-26bf-405a-a8bc-76eb6025f5eb%40googlegroups.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 https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAP7f1AgxHBTpqXHo4-8aKBWHHTuzAeKL2U9FLiJqKAAyenDLLw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
