01:06 <mtrbot-ml> [mattermost] <sb10q> @astro nice!

07:19 <sb0> forwarding a question that was emailed to me: "We would like to use the Urukul DDS to run some of our AOMs around 420-430 MHz. Do you foresee this as a problem? We are expecting we'll have to amplify these outputs a little more to compensate for reduced signal power at these frequencies."

09:32 <rjo> the power is down by whatever the filter curve has at that frequency (less than 2.6 dB insertion loss) plus the sinc roll off of the DDS output (a few dB). expect ~6 dBm max output.

17:31 <whitequark> sb0: i just discovered https://pypi.org/project/redbaron/, which could be a potential replacement for pythonparser. it supports every feature up to 3.7.

17:31 <whitequark> that said my hopes for it are not very high as i suspect it will be significantly slower

17:37 <rjo> interesting. could they in turn use pythonparser?

17:38 <whitequark> pythonparser would not work for their purposes

17:38 <whitequark> pythonparser preserves source locations for most interesting nodes, whereas redbaron preserves all whitespace as-is

17:38 <whitequark> e.g. pythonparser doesn't even track comma locations.

17:39 <whitequark> it also doesn't have a serializer, in part because redbaron uses a different fundamental approach, one well suited for a refactoring tool

17:39 <whitequark> whereas pythonparser is fundamentally a parser for a language frontend