9. SupportNew

If you find pycos useful:

  • New: Now there is a discussion forum which is more convenient than github / sourceforge for users to discuss, post issues and engage with other users. Members will also be notified of new releases, developments. Please join the forum and describe your use cases, interesting examples in Uses along with any suggestions for improvement. This is essential to further development, enchancements and maintenance. If you do not wish to post in public, would like to discuss or to know more about this platform, contact email me.

  • If you use pycos in academic/research work, please cite pycos as:

    Giridhar Pemmasani, "pycos: Concurrent, Asynchronous, Distributed,
  Communicating Tasks with Python", https://pycos.org, 2017.

  • Consider contributing to the project. The source code is available on GitHub. Here are a few suggestions:

    1. More examples (real-world, academic, or demonstrative examples) can be added. Evolutionary / genetic computing, swarm intelligence, for example, can be implemented with Distributed Communicating Tasks (dispycos).

    2. Documentation can be improved.

    3. Support for fault tolerance can be added to Scheduler.

    4. Different schedulers (e.g., priority scheduling for scheduling tasks) for dispycos (for managing distributed tasks) can be implemented.

    5. Name resolution of resources is not currently cached, so if, for example, a task is located again, pycos sends lookup request and waits for results. Caching can improve performance, but it means resources may need to be validated (periodically), pruned if too many resources are cached etc. Alternatley, external libraries such as Redis can be supported to store location information of resources.

    6. Comments in the code with ‘TODO’ are ideas / improvements / potential issues; these can be addressed.

  • Recommend / Share pycos with the links below :