EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: EPICS Python Question
From: "Kasemir, Kay" <[email protected]>
To: Elder Matias <[email protected]>, "[email protected]" <[email protected]>
Date: Tue, 30 Sep 2014 12:45:33 +0000
Hello:

For SNS beam line updates we started using cothread, but now prefer https://pypi.python.org/pypi/CaChannel

cothread has a very nice API, but it uses its own type of cooperative threads which prohibit use of plain python threads.

We need to use both a CA client and a CA server (http://code.google.com/p/pcaspy/) within the same python program, and would like to have the option of using additional python libraries which in turn might create their own threads. So far, we found no issues when combining pcaspy and CaChannel within the same python program.

Thanks,
Kay


On Sep 29, 2014, at 10:18 PM, Elder Matias <[email protected]<mailto:[email protected]>>
 wrote:

Quick question....



I have a project we may be taking on for one of our clients.  I am considering EPICS.  Still have a few decision to make.



Obviously the low-level software is going to be C/C++.  All our new development these days are python and django.   What is the preferred python binding to EPICS in the community these days?



Thanks,
Elder



Elder Matias
President and CEO
Mighty Oaks  (www.mightyoaks.com<http://www.mightyoaks.com>)



Technology Simplified!
Creating Secure Differentiated Experiences with our partners Dassualt Systems, SoftExpert and Sophos.



________________________________

This e-mail is intended only for the person to whom it is addressed (the "addressee") and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use that a person other than the addressee makes of this communication is prohibited and any reliance or decisions made based on it, are the responsibility of such person. We accept no responsibility for any loss or damages suffered by any person other than the addressee as a result of decisions made or actions taken based on this communication or otherwise. If you received this in error, please contact the sender and destroy all copies of this e-mail.

Ce courrier est strictement reservé a l'usage de la personne a qui il est adressé (le destinataire). Il peut contenir de l'information privilégiée et confidentielle. L'examen, la réexpédition et la diffusion de ce message par une personne autre que son destinataire est interdite. Nous refusons toute responsabilité a l'égard des pertes ou des dommages subis par une personne autre que le destinataire par suite de decisions ou de mesures fondées sur le contenu de cette communication ou autrement. Si vous avez recu ce courrier par erreur, veuillez communiquer avec son expéditeur et en détruire toutes les copies.



Replies:
Re: EPICS Python Question Shen, Guobao
RE: EPICS Python Question michael.abbott
References:
EPICS Python Question Elder Matias

Navigate by Date:
Prev: Re: EPICS Python Question Hugo Slepicka
Next: Re: EPICS Python Question Shen, Guobao
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: EPICS Python Question Hugo Slepicka
Next: Re: EPICS Python Question Shen, Guobao
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024