Hi Amine,
On 10/15/2018 03:53 PM, Amine Aboufirass wrote:
Dear All,
I am a python developer interested in contributing to the sfepy project.
Contributions are welcome, thanks for considering it!
There is quite a bit of material in the "How to contribute" page ( http://sfepy.org/doc-devel/developer_guide.html#how-to-contribute). So far I have been able to :
- fork repository to my github account - clone forked repository into my local computer - look through issues in sfepy github page for opportunities to help resolve salient issues. I am thinking about this one in particular https://github.com/sfepy/sfepy/issues/367 - Look into forking workflow in Atlassian website ( https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow ) - Pursue basic git tutorials. so far I have only experience working with svn vcs.
FYI: This is a very insightful git tutorial: http://www.eecs.harvard.edu/~cduan/technical/git/
I am confused abut how to properly set up a standalone sfepy development environment in conda. Of course installing a regular environment is easy
*conda install -c conda-forge sfepy*
The above command seems to take care of all dependencies, including the python installation itself. However I don't understand how this can be combined with *git clone *such that I can install the cloned fork within conda environment. How are the dependencies handled? What of the python version dependency? I do not see these anywhere in the repository, it seems to only contain sfepy scripts and modules.
With conda, I would propose installing the dependencies like you did, then removing the installed sfepy, and cloning your fork from github (you have this already). Then you can just use the in-place build (see the installation docs) and work in the cloned directory, without installing sfepy. Does it make sense? Do not hesitate to ask more.
Best regards, r.