1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 <2014> 2015 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 <2014> 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: EPICS Python Question |
From: | Hugo Slepicka <[email protected]> |
To: | "Shen, Guobao" <[email protected]> |
Cc: | Elder Matias <[email protected]>, EPICS <[email protected]> |
Date: | Tue, 30 Sep 2014 08:59:38 -0300 |
Here at NSLS II, we use cothread a lot, which is developed by Diamond.
Guobao
From: [email protected] [[email protected]] on behalf of Jemian, Pete R. [[email protected]]
Sent: Monday, September 29, 2014 10:27 PM
To: Elder Matias; EPICS
Subject: RE: EPICS Python Question
Not sure there is a single "preferred" python across the EPICS community. At APS, the preferred binding is PyEpics.
Pete Jemian
Sent from my Samsung Galaxy Note® II
-------- Original message --------
From: Elder Matias <[email protected]>
Date: 2014/09/29 9:19 PM (GMT-06:00)
To: [email protected]
Subject: EPICS Python Question
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)
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.