Development of an internal social media platform with personalised dashboards for students
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.

METADATA 14KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500
  1. Metadata-Version: 2.0
  2. Name: celery
  3. Version: 3.1.26.post2
  4. Summary: Distributed Task Queue
  5. Home-page: http://celeryproject.org
  6. Author: Ask Solem
  7. Author-email: ask@celeryproject.org
  8. License: BSD
  9. Description-Content-Type: UNKNOWN
  10. Platform: any
  11. Classifier: Development Status :: 5 - Production/Stable
  12. Classifier: License :: OSI Approved :: BSD License
  13. Classifier: Topic :: System :: Distributed Computing
  14. Classifier: Topic :: Software Development :: Object Brokering
  15. Classifier: Programming Language :: Python
  16. Classifier: Programming Language :: Python :: 2
  17. Classifier: Programming Language :: Python :: 2.6
  18. Classifier: Programming Language :: Python :: 2.7
  19. Classifier: Programming Language :: Python :: 3
  20. Classifier: Programming Language :: Python :: 3.3
  21. Classifier: Programming Language :: Python :: 3.4
  22. Classifier: Programming Language :: Python :: Implementation :: CPython
  23. Classifier: Programming Language :: Python :: Implementation :: PyPy
  24. Classifier: Programming Language :: Python :: Implementation :: Jython
  25. Classifier: Operating System :: OS Independent
  26. Classifier: Operating System :: POSIX
  27. Classifier: Operating System :: Microsoft :: Windows
  28. Classifier: Operating System :: MacOS :: MacOS X
  29. Requires-Dist: pytz (>dev)
  30. Requires-Dist: billiard (<3.4,>=3.3.0.23)
  31. Requires-Dist: kombu (<3.1,>=3.0.37)
  32. Provides-Extra: auth
  33. Requires-Dist: pyOpenSSL; extra == 'auth'
  34. Provides-Extra: beanstalk
  35. Requires-Dist: beanstalkc; extra == 'beanstalk'
  36. Provides-Extra: cassandra
  37. Requires-Dist: pycassa; extra == 'cassandra'
  38. Provides-Extra: couchbase
  39. Requires-Dist: couchbase; extra == 'couchbase'
  40. Provides-Extra: couchdb
  41. Requires-Dist: couchdb; extra == 'couchdb'
  42. Provides-Extra: eventlet
  43. Requires-Dist: eventlet; extra == 'eventlet'
  44. Provides-Extra: gevent
  45. Requires-Dist: gevent; extra == 'gevent'
  46. Provides-Extra: librabbitmq
  47. Requires-Dist: librabbitmq (>=1.6.1); extra == 'librabbitmq'
  48. Provides-Extra: memcache
  49. Requires-Dist: pylibmc; extra == 'memcache'
  50. Provides-Extra: mongodb
  51. Requires-Dist: pymongo (>=2.6.2); extra == 'mongodb'
  52. Provides-Extra: msgpack
  53. Requires-Dist: msgpack-python (>=0.3.0); extra == 'msgpack'
  54. Provides-Extra: pyro
  55. Requires-Dist: pyro4; extra == 'pyro'
  56. Provides-Extra: redis
  57. Requires-Dist: redis (>=2.8.0); extra == 'redis'
  58. Provides-Extra: slmq
  59. Requires-Dist: softlayer-messaging (>=1.0.3); extra == 'slmq'
  60. Provides-Extra: sqlalchemy
  61. Requires-Dist: sqlalchemy; extra == 'sqlalchemy'
  62. Provides-Extra: sqs
  63. Requires-Dist: boto (>=2.13.3); extra == 'sqs'
  64. Provides-Extra: threads
  65. Requires-Dist: threadpool; extra == 'threads'
  66. Provides-Extra: yaml
  67. Requires-Dist: PyYAML (>=3.10); extra == 'yaml'
  68. Provides-Extra: zeromq
  69. Requires-Dist: pyzmq (>=13.1.0); extra == 'zeromq'
  70. Provides-Extra: zookeeper
  71. Requires-Dist: kazoo (>=1.3.1); extra == 'zookeeper'
  72. =================================
  73. celery - Distributed Task Queue
  74. =================================
  75. .. image:: http://cloud.github.com/downloads/celery/celery/celery_128.png
  76. :Version: 3.1.26 (Cipater)
  77. :Web: http://celeryproject.org/
  78. :Download: http://pypi.python.org/pypi/celery/
  79. :Source: http://github.com/celery/celery/
  80. :Keywords: task queue, job queue, asynchronous, async, rabbitmq, amqp, redis,
  81. python, webhooks, queue, distributed
  82. --
  83. What is a Task Queue?
  84. =====================
  85. Task queues are used as a mechanism to distribute work across threads or
  86. machines.
  87. A task queue's input is a unit of work, called a task, dedicated worker
  88. processes then constantly monitor the queue for new work to perform.
  89. Celery communicates via messages, usually using a broker
  90. to mediate between clients and workers. To initiate a task a client puts a
  91. message on the queue, the broker then delivers the message to a worker.
  92. A Celery system can consist of multiple workers and brokers, giving way
  93. to high availability and horizontal scaling.
  94. Celery is a library written in Python, but the protocol can be implemented in
  95. any language. So far there's RCelery_ for the Ruby programming language, and a
  96. `PHP client`, but language interoperability can also be achieved
  97. by using webhooks.
  98. .. _RCelery: http://leapfrogdevelopment.github.com/rcelery/
  99. .. _`PHP client`: https://github.com/gjedeer/celery-php
  100. .. _`using webhooks`:
  101. http://docs.celeryproject.org/en/latest/userguide/remote-tasks.html
  102. What do I need?
  103. ===============
  104. Celery version 3.0 runs on,
  105. - Python (2.5, 2.6, 2.7, 3.2, 3.3)
  106. - PyPy (1.8, 1.9)
  107. - Jython (2.5, 2.7).
  108. This is the last version to support Python 2.5,
  109. and from Celery 3.1, Python 2.6 or later is required.
  110. The last version to support Python 2.4 was Celery series 2.2.
  111. *Celery* is usually used with a message broker to send and receive messages.
  112. The RabbitMQ, Redis transports are feature complete,
  113. but there's also experimental support for a myriad of other solutions, including
  114. using SQLite for local development.
  115. *Celery* can run on a single machine, on multiple machines, or even
  116. across datacenters.
  117. Get Started
  118. ===========
  119. If this is the first time you're trying to use Celery, or you are
  120. new to Celery 3.0 coming from previous versions then you should read our
  121. getting started tutorials:
  122. - `First steps with Celery`_
  123. Tutorial teaching you the bare minimum needed to get started with Celery.
  124. - `Next steps`_
  125. A more complete overview, showing more features.
  126. .. _`First steps with Celery`:
  127. http://docs.celeryproject.org/en/latest/getting-started/first-steps-with-celery.html
  128. .. _`Next steps`:
  129. http://docs.celeryproject.org/en/latest/getting-started/next-steps.html
  130. Celery is...
  131. ============
  132. - **Simple**
  133. Celery is easy to use and maintain, and does *not need configuration files*.
  134. It has an active, friendly community you can talk to for support,
  135. including a `mailing-list`_ and and an IRC channel.
  136. Here's one of the simplest applications you can make::
  137. from celery import Celery
  138. app = Celery('hello', broker='amqp://guest@localhost//')
  139. @app.task
  140. def hello():
  141. return 'hello world'
  142. - **Highly Available**
  143. Workers and clients will automatically retry in the event
  144. of connection loss or failure, and some brokers support
  145. HA in way of *Master/Master* or *Master/Slave* replication.
  146. - **Fast**
  147. A single Celery process can process millions of tasks a minute,
  148. with sub-millisecond round-trip latency (using RabbitMQ,
  149. py-librabbitmq, and optimized settings).
  150. - **Flexible**
  151. Almost every part of *Celery* can be extended or used on its own,
  152. Custom pool implementations, serializers, compression schemes, logging,
  153. schedulers, consumers, producers, autoscalers, broker transports and much more.
  154. It supports...
  155. ==============
  156. - **Message Transports**
  157. - RabbitMQ_, Redis_,
  158. - MongoDB_ (experimental), Amazon SQS (experimental),
  159. - CouchDB_ (experimental), SQLAlchemy_ (experimental),
  160. - Django ORM (experimental), `IronMQ`_
  161. - and more...
  162. - **Concurrency**
  163. - Prefork, Eventlet_, gevent_, threads/single threaded
  164. - **Result Stores**
  165. - AMQP, Redis
  166. - memcached, MongoDB
  167. - SQLAlchemy, Django ORM
  168. - Apache Cassandra, IronCache
  169. - **Serialization**
  170. - *pickle*, *json*, *yaml*, *msgpack*.
  171. - *zlib*, *bzip2* compression.
  172. - Cryptographic message signing.
  173. .. _`Eventlet`: http://eventlet.net/
  174. .. _`gevent`: http://gevent.org/
  175. .. _RabbitMQ: http://rabbitmq.com
  176. .. _Redis: http://redis.io
  177. .. _MongoDB: http://mongodb.org
  178. .. _Beanstalk: http://kr.github.com/beanstalkd
  179. .. _CouchDB: http://couchdb.apache.org
  180. .. _SQLAlchemy: http://sqlalchemy.org
  181. .. _`IronMQ`: http://iron.io
  182. Framework Integration
  183. =====================
  184. Celery is easy to integrate with web frameworks, some of which even have
  185. integration packages:
  186. +--------------------+------------------------+
  187. | `Django`_ | not needed |
  188. +--------------------+------------------------+
  189. | `Pyramid`_ | `pyramid_celery`_ |
  190. +--------------------+------------------------+
  191. | `Pylons`_ | `celery-pylons`_ |
  192. +--------------------+------------------------+
  193. | `Flask`_ | not needed |
  194. +--------------------+------------------------+
  195. | `web2py`_ | `web2py-celery`_ |
  196. +--------------------+------------------------+
  197. | `Tornado`_ | `tornado-celery`_ |
  198. +--------------------+------------------------+
  199. The integration packages are not strictly necessary, but they can make
  200. development easier, and sometimes they add important hooks like closing
  201. database connections at ``fork``.
  202. .. _`Django`: http://djangoproject.com/
  203. .. _`Pylons`: http://pylonsproject.org/
  204. .. _`Flask`: http://flask.pocoo.org/
  205. .. _`web2py`: http://web2py.com/
  206. .. _`Bottle`: http://bottlepy.org/
  207. .. _`Pyramid`: http://docs.pylonsproject.org/en/latest/docs/pyramid.html
  208. .. _`pyramid_celery`: http://pypi.python.org/pypi/pyramid_celery/
  209. .. _`django-celery`: http://pypi.python.org/pypi/django-celery
  210. .. _`celery-pylons`: http://pypi.python.org/pypi/celery-pylons
  211. .. _`web2py-celery`: http://code.google.com/p/web2py-celery/
  212. .. _`Tornado`: http://www.tornadoweb.org/
  213. .. _`tornado-celery`: http://github.com/mher/tornado-celery/
  214. .. _celery-documentation:
  215. Documentation
  216. =============
  217. The `latest documentation`_ with user guides, tutorials and API reference
  218. is hosted at Read The Docs.
  219. .. _`latest documentation`: http://docs.celeryproject.org/en/latest/
  220. .. _celery-installation:
  221. Installation
  222. ============
  223. You can install Celery either via the Python Package Index (PyPI)
  224. or from source.
  225. To install using `pip`,::
  226. $ pip install -U Celery
  227. To install using `easy_install`,::
  228. $ easy_install -U Celery
  229. .. _bundles:
  230. Bundles
  231. -------
  232. Celery also defines a group of bundles that can be used
  233. to install Celery and the dependencies for a given feature.
  234. You can specify these in your requirements or on the ``pip`` comand-line
  235. by using brackets. Multiple bundles can be specified by separating them by
  236. commas.
  237. ::
  238. $ pip install "celery[librabbitmq]"
  239. $ pip install "celery[librabbitmq,redis,auth,msgpack]"
  240. The following bundles are available:
  241. Serializers
  242. ~~~~~~~~~~~
  243. :celery[auth]:
  244. for using the auth serializer.
  245. :celery[msgpack]:
  246. for using the msgpack serializer.
  247. :celery[yaml]:
  248. for using the yaml serializer.
  249. Concurrency
  250. ~~~~~~~~~~~
  251. :celery[eventlet]:
  252. for using the eventlet pool.
  253. :celery[gevent]:
  254. for using the gevent pool.
  255. :celery[threads]:
  256. for using the thread pool.
  257. Transports and Backends
  258. ~~~~~~~~~~~~~~~~~~~~~~~
  259. :celery[librabbitmq]:
  260. for using the librabbitmq C library.
  261. :celery[redis]:
  262. for using Redis as a message transport or as a result backend.
  263. :celery[mongodb]:
  264. for using MongoDB as a message transport (*experimental*),
  265. or as a result backend (*supported*).
  266. :celery[sqs]:
  267. for using Amazon SQS as a message transport (*experimental*).
  268. :celery[memcache]:
  269. for using memcached as a result backend.
  270. :celery[cassandra]:
  271. for using Apache Cassandra as a result backend.
  272. :celery[couchdb]:
  273. for using CouchDB as a message transport (*experimental*).
  274. :celery[couchbase]:
  275. for using CouchBase as a result backend.
  276. :celery[beanstalk]:
  277. for using Beanstalk as a message transport (*experimental*).
  278. :celery[zookeeper]:
  279. for using Zookeeper as a message transport.
  280. :celery[zeromq]:
  281. for using ZeroMQ as a message transport (*experimental*).
  282. :celery[sqlalchemy]:
  283. for using SQLAlchemy as a message transport (*experimental*),
  284. or as a result backend (*supported*).
  285. :celery[pyro]:
  286. for using the Pyro4 message transport (*experimental*).
  287. :celery[slmq]:
  288. for using the SoftLayer Message Queue transport (*experimental*).
  289. .. _celery-installing-from-source:
  290. Downloading and installing from source
  291. --------------------------------------
  292. Download the latest version of Celery from
  293. http://pypi.python.org/pypi/celery/
  294. You can install it by doing the following,::
  295. $ tar xvfz celery-0.0.0.tar.gz
  296. $ cd celery-0.0.0
  297. $ python setup.py build
  298. # python setup.py install
  299. The last command must be executed as a privileged user if
  300. you are not currently using a virtualenv.
  301. .. _celery-installing-from-git:
  302. Using the development version
  303. -----------------------------
  304. With pip
  305. ~~~~~~~~
  306. The Celery development version also requires the development
  307. versions of ``kombu``, ``amqp`` and ``billiard``.
  308. You can install the latest snapshot of these using the following
  309. pip commands::
  310. $ pip install https://github.com/celery/celery/zipball/master#egg=celery
  311. $ pip install https://github.com/celery/billiard/zipball/master#egg=billiard
  312. $ pip install https://github.com/celery/py-amqp/zipball/master#egg=amqp
  313. $ pip install https://github.com/celery/kombu/zipball/master#egg=kombu
  314. With git
  315. ~~~~~~~~
  316. Please the Contributing section.
  317. .. _getting-help:
  318. Getting Help
  319. ============
  320. .. _mailing-list:
  321. Mailing list
  322. ------------
  323. For discussions about the usage, development, and future of celery,
  324. please join the `celery-users`_ mailing list.
  325. .. _`celery-users`: http://groups.google.com/group/celery-users/
  326. .. _irc-channel:
  327. IRC
  328. ---
  329. Come chat with us on IRC. The **#celery** channel is located at the `Freenode`_
  330. network.
  331. .. _`Freenode`: http://freenode.net
  332. .. _bug-tracker:
  333. Bug tracker
  334. ===========
  335. If you have any suggestions, bug reports or annoyances please report them
  336. to our issue tracker at http://github.com/celery/celery/issues/
  337. .. _wiki:
  338. Wiki
  339. ====
  340. http://wiki.github.com/celery/celery/
  341. .. _contributing-short:
  342. Contributing
  343. ============
  344. Development of `celery` happens at Github: http://github.com/celery/celery
  345. You are highly encouraged to participate in the development
  346. of `celery`. If you don't like Github (for some reason) you're welcome
  347. to send regular patches.
  348. Be sure to also read the `Contributing to Celery`_ section in the
  349. documentation.
  350. .. _`Contributing to Celery`:
  351. http://docs.celeryproject.org/en/master/contributing.html
  352. .. _license:
  353. License
  354. =======
  355. This software is licensed under the `New BSD License`. See the ``LICENSE``
  356. file in the top distribution directory for the full license text.
  357. .. # vim: syntax=rst expandtab tabstop=4 shiftwidth=4 shiftround
  358. .. image:: https://d2weczhvl823v0.cloudfront.net/celery/celery/trend.png
  359. :alt: Bitdeli badge
  360. :target: https://bitdeli.com/free