On Tuesday, 29 November 2016 05:57:09 UTC+11, Samuel Lelievre wrote: > > Dear sage-devel, > > This is a follow-up to a discussion on sage-support [0] in which > the original poster asks a question which I will summarize as: > > Having written some amount of Sage code for a project, > how can I best package it and share it with the community? > > Among the answers, Vincent suggests turning the code into a pip-installable > Python package for Sage, and points to a sample such package [1], made last > week at Sage Days 79 precisely to help people do that. > > Vincent also points to the wiki page [2], which consists in a list > of external packages for Sage, some pip-installable, some not. > > A bit later in the discussion, William writes: > > > It would be great if somebody could create some sort of index > > of such packages, which we could link to (or include) on sagemath.org. > > > > This might eventually involve using some sort of tagging > > (or searching) of https://pypi.python.org/pypi and/or github. > > For now, this could just be a Github wiki page, which gets updated > > as we become aware of packages, and which we link to from sagemath.org. > > > > Thoughts? > > I'm moving the discussion to sage-devel. > > The pages "SageMath external packages" [2] and "Code sharing workflow" [3] > were created in May 2016 following discussions on various Sage mailing > lists > and at Sage Days 77 about modularization and packaging of Sage. > > The page [2] was a preliminary attempt at "some sort of index of such > packages", and has a link to "Packages on PyPI matching 'sagemath'" [4], > which is intended as "using some sort of tagging or searching of PyPI". > > It would certainly be nice to have a similar tagging or searching of > GitHub, > bitbucket, and other code repositories, to detect external packages for > Sage. > > Probably the list at [2] should be turned into a better format, maybe a > json > or yaml file or some appropriate database format, and be made accessible > and > visible at some page on sagemath.org. > > Entries in a database of Sage packages might have the following fields: > > - package name > - alternate names, if applicable > - author(s) > - maintainer(s) > - short description > - long description > - keywords > - link to package home page > - link to code repository > - link to documentation > - license > - date package was created > - type of package (spkg, pip-installable, ...) > - relevant Sage trac tickets, > - discussions on sage-devel or other media > - maintenance status > - ... > > We might also check how other communities index external packages, > for instance Astropy, GAP, Julia, ... > > [0] https://groups.google.com/d/msg/sage-support/xsDt7TUjZkM/iOSBXfK7CgAJ > [1] https://github.com/nthiery/sage_sample > [2] https://wiki.sagemath.org/SageMathExternalPackages > [3] https://wiki.sagemath.org/CodeSharingWorkflow > [4] > https://pypi.python.org/pypi?%3Aaction=search&term=sagemath&submit=search > > Best, Samuel >
Thanks Samuel, It probably would also be useful to have a bibliography type field. i have been developing Sage and Python code for use in my exploration of bent functions and their strongly regular Cayley graphs as described in my recent (today) talk; Classifying bent functions by their Cayley graphs, using Sage <https://sites.google.com/site/paulleopardi/Leopardi-ACCMCC-2016-talk.pdf?attredirects=0&d=1>, 40 ACCMCC, 2016. The code (and manuscript) repository is at https://github.com/penguian/Boolean-Cayley-graphs There is also a public SageMathCloud directory at https://cloud.sagemath.com/projects/80f4c9e7-8a37-4f59-82e7-aa179ec0b652/files/Boolean-Cayley-graphs/ with extra SageMathCloud worksheets. I am in the process of updating the code and especially the comments to conform to SageMath expectations, and porting some of the Sage code to Python, where sensible, but some will remain as Sage code. If I create a PyPI package, what am i supposed to do with my Sage code that is outside of the boolean_cayley_graphs Python package directory? Also, how can I ask for people to review my code short of trying to submit it into Sage proper? All the best,Paul -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
