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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Spawn error when pyepics device puts into nonexistent PV |
From: | "Marco A. Barra Montevechi Filho via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, "Marco A. Barra Montevechi Filho" <marco.filho at lnls.br> |
Date: | Mon, 18 Sep 2023 21:14:59 +0000 |
I just figured the return values are None for get fail and for put fail, so that can be used for error checking.
Sorry for the inconvenience, Marco From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Marco A. Barra Montevechi Filho via Tech-talk <tech-talk at aps.anl.gov>
Sent: 18 September 2023 17:39 To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: Spawn error when pyepics device puts into nonexistent PV
Hi all, im using pyepics device to interact with plugins.
I tried doing: a = epics.Device("A", delim=":",attrs=["B"]) a.put("B", 4) Since "A:B" is a nonexistent PV in my environment, i would expect an error or at least a warning here, but i get nothing. It seems the attribute is a PV object and PV also dont have an option for raising an exception when put to nonexistent things: a = epics.PV("A:B") a.put(4) Also returns no error. Is there any way to make this happen? Would a PR in pyepics be welcome in this direction? Thanks, Marco Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente. Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately. |