m2m模型翻译
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

310 lines
12 KiB

6 months ago
  1. Metadata-Version: 2.1
  2. Name: sympy
  3. Version: 1.10.1
  4. Summary: Computer algebra system (CAS) in Python
  5. Home-page: https://sympy.org
  6. Author: SymPy development team
  7. Author-email: sympy@googlegroups.com
  8. License: BSD
  9. Keywords: Math CAS
  10. Platform: UNKNOWN
  11. Classifier: License :: OSI Approved :: BSD License
  12. Classifier: Operating System :: OS Independent
  13. Classifier: Programming Language :: Python
  14. Classifier: Topic :: Scientific/Engineering
  15. Classifier: Topic :: Scientific/Engineering :: Mathematics
  16. Classifier: Topic :: Scientific/Engineering :: Physics
  17. Classifier: Programming Language :: Python :: 3
  18. Classifier: Programming Language :: Python :: 3.7
  19. Classifier: Programming Language :: Python :: 3.8
  20. Classifier: Programming Language :: Python :: 3.9
  21. Classifier: Programming Language :: Python :: 3.10
  22. Classifier: Programming Language :: Python :: 3 :: Only
  23. Classifier: Programming Language :: Python :: Implementation :: CPython
  24. Classifier: Programming Language :: Python :: Implementation :: PyPy
  25. Requires-Python: >=3.7
  26. Description-Content-Type: text/markdown
  27. License-File: LICENSE
  28. License-File: AUTHORS
  29. Requires-Dist: mpmath (>=0.19)
  30. # SymPy
  31. [![pypi version](https://img.shields.io/pypi/v/sympy.svg)](https://pypi.python.org/pypi/sympy)
  32. [![Build status](https://secure.travis-ci.org/sympy/sympy.svg?branch=master)](https://travis-ci.org/sympy/sympy)
  33. [![Join the chat at https://gitter.im/sympy/sympy](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/sympy/sympy?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
  34. [![Zenodo Badge](https://zenodo.org/badge/18918/sympy/sympy.svg)](https://zenodo.org/badge/latestdoi/18918/sympy/sympy)
  35. [![codecov Badge](https://codecov.io/gh/sympy/sympy/branch/master/graph/badge.svg)](https://codecov.io/gh/sympy/sympy)
  36. [![SymPy Banner](https://github.com/sympy/sympy/raw/master/banner.svg)](https://sympy.org/)
  37. See the [AUTHORS](AUTHORS) file for the list of authors.
  38. And many more people helped on the SymPy mailing list, reported bugs,
  39. helped organize SymPy's participation in the Google Summer of Code, the
  40. Google Highly Open Participation Contest, Google Code-In, wrote and
  41. blogged about SymPy...
  42. License: New BSD License (see the [LICENSE](LICENSE) file for details) covers all
  43. files in the sympy repository unless stated otherwise.
  44. Our mailing list is at
  45. <https://groups.google.com/forum/?fromgroups#!forum/sympy>.
  46. We have a community chat at [Gitter](https://gitter.im/sympy/sympy). Feel
  47. free to ask us anything there. We have a very welcoming and helpful
  48. community.
  49. ## Download
  50. The recommended installation method is through Anaconda,
  51. <https://www.anaconda.com/download/>
  52. You can also get the latest version of SymPy from
  53. <https://pypi.python.org/pypi/sympy/>
  54. To get the git version do
  55. $ git clone https://github.com/sympy/sympy.git
  56. For other options (tarballs, debs, etc.), see
  57. <https://docs.sympy.org/dev/install.html>.
  58. ## Documentation and Usage
  59. For in-depth instructions on installation and building the
  60. documentation, see the [SymPy Documentation Style Guide](https://docs.sympy.org/dev/documentation-style-guide.html).
  61. Everything is at:
  62. <https://docs.sympy.org/>
  63. You can generate everything at the above site in your local copy of
  64. SymPy by:
  65. $ cd doc
  66. $ make html
  67. Then the docs will be in <span class="title-ref">\_build/html</span>. If
  68. you don't want to read that, here is a short usage:
  69. From this directory, start Python and:
  70. ``` python
  71. >>> from sympy import Symbol, cos
  72. >>> x = Symbol('x')
  73. >>> e = 1/cos(x)
  74. >>> print(e.series(x, 0, 10))
  75. 1 + x**2/2 + 5*x**4/24 + 61*x**6/720 + 277*x**8/8064 + O(x**10)
  76. ```
  77. SymPy also comes with a console that is a simple wrapper around the
  78. classic python console (or IPython when available) that loads the SymPy
  79. namespace and executes some common commands for you.
  80. To start it, issue:
  81. $ bin/isympy
  82. from this directory, if SymPy is not installed or simply:
  83. $ isympy
  84. if SymPy is installed.
  85. ## Installation
  86. SymPy has a hard dependency on the [mpmath](http://mpmath.org/) library
  87. (version \>= 0.19). You should install it first, please refer to the
  88. mpmath installation guide:
  89. <https://github.com/fredrik-johansson/mpmath#1-download--installation>
  90. To install SymPy using PyPI, run the following command:
  91. $ pip install sympy
  92. To install SymPy using Anaconda, run the following command:
  93. $ conda install -c anaconda sympy
  94. To install SymPy from GitHub source, first clone SymPy using `git`:
  95. $ git clone https://github.com/sympy/sympy.git
  96. Then, in the `sympy` repository that you cloned, simply run:
  97. $ python setup.py install
  98. See <https://docs.sympy.org/dev/install.html> for more information.
  99. ## Contributing
  100. We welcome contributions from anyone, even if you are new to open
  101. source. Please read our [Introduction to Contributing](https://github.com/sympy/sympy/wiki/Introduction-to-contributing)
  102. page and the [SymPy Documentation Style Guide](https://docs.sympy.org/dev/documentation-style-guide.html). If you
  103. are new and looking for some way to contribute, a good place to start is
  104. to look at the issues tagged [Easy to Fix](https://github.com/sympy/sympy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+to+Fix%22).
  105. Please note that all participants in this project are expected to follow
  106. our Code of Conduct. By participating in this project you agree to abide
  107. by its terms. See [CODE\_OF\_CONDUCT.md](CODE_OF_CONDUCT.md).
  108. ## Tests
  109. To execute all tests, run:
  110. $./setup.py test
  111. in the current directory.
  112. For the more fine-grained running of tests or doctests, use `bin/test`
  113. or respectively `bin/doctest`. The master branch is automatically tested
  114. by Travis CI.
  115. To test pull requests, use
  116. [sympy-bot](https://github.com/sympy/sympy-bot).
  117. ## Regenerate Experimental <span class="title-ref">LaTeX</span> Parser/Lexer
  118. The parser and lexer were generated with the [ANTLR4](http://antlr4.org)
  119. toolchain in `sympy/parsing/latex/_antlr` and checked into the repo.
  120. Presently, most users should not need to regenerate these files, but
  121. if you plan to work on this feature, you will need the `antlr4`
  122. command-line tool (and you must ensure that it is in your `PATH`).
  123. One way to get it is:
  124. $ conda install -c conda-forge antlr=4.7.2
  125. Alternatively, follow the instructions on the ANTLR website and download
  126. the `antlr-4.7.2-complete.jar`. Then export the `CLASSPATH` as instructed
  127. and instead of creating `antlr4` as an alias, make it an executable file
  128. with the following contents:
  129. ``` bash
  130. #!/bin/bash
  131. java -jar /usr/local/lib/antlr-4.7.2-complete.jar "$@"
  132. ```
  133. After making changes to `sympy/parsing/latex/LaTeX.g4`, run:
  134. $ ./setup.py antlr
  135. ## Clean
  136. To clean everything (thus getting the same tree as in the repository):
  137. $ ./setup.py clean
  138. You can also clean things with git using:
  139. $ git clean -Xdf
  140. which will clear everything ignored by `.gitignore`, and:
  141. $ git clean -df
  142. to clear all untracked files. You can revert the most recent changes in
  143. git with:
  144. $ git reset --hard
  145. WARNING: The above commands will all clear changes you may have made,
  146. and you will lose them forever. Be sure to check things with `git
  147. status`, `git diff`, `git clean -Xn`, and `git clean -n` before doing any
  148. of those.
  149. ## Bugs
  150. Our issue tracker is at <https://github.com/sympy/sympy/issues>. Please
  151. report any bugs that you find. Or, even better, fork the repository on
  152. GitHub and create a pull request. We welcome all changes, big or small,
  153. and we will help you make the pull request if you are new to git (just
  154. ask on our mailing list or Gitter Channel). If you further have any queries, you can find answers
  155. on Stack Overflow using the [sympy](https://stackoverflow.com/questions/tagged/sympy) tag.
  156. ## Brief History
  157. SymPy was started by Ondřej Čertík in 2005, he wrote some code during
  158. the summer, then he wrote some more code during summer 2006. In February
  159. 2007, Fabian Pedregosa joined the project and helped fix many things,
  160. contributed documentation, and made it alive again. 5 students (Mateusz
  161. Paprocki, Brian Jorgensen, Jason Gedge, Robert Schwarz, and Chris Wu)
  162. improved SymPy incredibly during summer 2007 as part of the Google
  163. Summer of Code. Pearu Peterson joined the development during the summer
  164. 2007 and he has made SymPy much more competitive by rewriting the core
  165. from scratch, which has made it from 10x to 100x faster. Jurjen N.E. Bos
  166. has contributed pretty-printing and other patches. Fredrik Johansson has
  167. written mpmath and contributed a lot of patches.
  168. SymPy has participated in every Google Summer of Code since 2007. You
  169. can see <https://github.com/sympy/sympy/wiki#google-summer-of-code> for
  170. full details. Each year has improved SymPy by bounds. Most of SymPy's
  171. development has come from Google Summer of Code students.
  172. In 2011, Ondřej Čertík stepped down as lead developer, with Aaron
  173. Meurer, who also started as a Google Summer of Code student, taking his
  174. place. Ondřej Čertík is still active in the community but is too busy
  175. with work and family to play a lead development role.
  176. Since then, a lot more people have joined the development and some
  177. people have also left. You can see the full list in doc/src/aboutus.rst,
  178. or online at:
  179. <https://docs.sympy.org/dev/aboutus.html#sympy-development-team>
  180. The git history goes back to 2007 when development moved from svn to hg.
  181. To see the history before that point, look at
  182. <https://github.com/sympy/sympy-old>.
  183. You can use git to see the biggest developers. The command:
  184. $ git shortlog -ns
  185. will show each developer, sorted by commits to the project. The command:
  186. $ git shortlog -ns --since="1 year"
  187. will show the top developers from the last year.
  188. ## Citation
  189. To cite SymPy in publications use
  190. > Meurer A, Smith CP, Paprocki M, Čertík O, Kirpichev SB, Rocklin M,
  191. > Kumar A, Ivanov S, Moore JK, Singh S, Rathnayake T, Vig S, Granger BE,
  192. > Muller RP, Bonazzi F, Gupta H, Vats S, Johansson F, Pedregosa F, Curry
  193. > MJ, Terrel AR, Roučka Š, Saboo A, Fernando I, Kulal S, Cimrman R,
  194. > Scopatz A. (2017) SymPy: symbolic computing in Python. *PeerJ Computer
  195. > Science* 3:e103 <https://doi.org/10.7717/peerj-cs.103>
  196. A BibTeX entry for LaTeX users is
  197. ``` bibtex
  198. @article{10.7717/peerj-cs.103,
  199. title = {SymPy: symbolic computing in Python},
  200. author = {Meurer, Aaron and Smith, Christopher P. and Paprocki, Mateusz and \v{C}ert\'{i}k, Ond\v{r}ej and Kirpichev, Sergey B. and Rocklin, Matthew and Kumar, Amit and Ivanov, Sergiu and Moore, Jason K. and Singh, Sartaj and Rathnayake, Thilina and Vig, Sean and Granger, Brian E. and Muller, Richard P. and Bonazzi, Francesco and Gupta, Harsh and Vats, Shivam and Johansson, Fredrik and Pedregosa, Fabian and Curry, Matthew J. and Terrel, Andy R. and Rou\v{c}ka, \v{S}t\v{e}p\'{a}n and Saboo, Ashutosh and Fernando, Isuru and Kulal, Sumith and Cimrman, Robert and Scopatz, Anthony},
  201. year = 2017,
  202. month = Jan,
  203. keywords = {Python, Computer algebra system, Symbolics},
  204. abstract = {
  205. SymPy is an open-source computer algebra system written in pure Python. It is built with a focus on extensibility and ease of use, through both interactive and programmatic applications. These characteristics have led SymPy to become a popular symbolic library for the scientific Python ecosystem. This paper presents the architecture of SymPy, a description of its features, and a discussion of select submodules. The supplementary material provides additional examples and further outlines details of the architecture and features of SymPy.
  206. },
  207. volume = 3,
  208. pages = {e103},
  209. journal = {PeerJ Computer Science},
  210. issn = {2376-5992},
  211. url = {https://doi.org/10.7717/peerj-cs.103},
  212. doi = {10.7717/peerj-cs.103}
  213. }
  214. ```
  215. SymPy is BSD licensed, so you are free to use it whatever you like, be
  216. it academic, commercial, creating forks or derivatives, as long as you
  217. copy the BSD statement if you redistribute it (see the LICENSE file for
  218. details). That said, although not required by the SymPy license, if it
  219. is convenient for you, please cite SymPy when using it in your work and
  220. also consider contributing all your changes back, so that we can
  221. incorporate it and all of us will benefit in the end.