Andrej Prsa

Could you possibly get a traceback to see what segfaults exactly? Running the script through gdb could shed light into what's going on.

I just tried running this code on my end and still cannot reproduce a segfault. Here is the output I'm getting: ``` (release) andrej@albireo:~/projects/phoebe/tests/segfault$ python segfault.py /home/andrej/projects/phoebe/venvs/release/lib/python3.10/site-packages/astropy/units/quantity.py:611: RuntimeWarning: invalid value...

After having looked into this in detail, I don't think it's feasible at all. WD optimizes invisible elements away so I would need to rewrite a good chunk of `light.f`...

This should now be a complete PR with a test case, version update and a changelog entry.

@kecnry: off the top of my head I don't know why pytest version would be an issue for astropy; I've not seen this elsewhere. It'll take some digging in to...

I refactored setup.py to try and find the source of the problem; I think the first issue is this: ``` Searching for gevent Downloading https://files.pythonhosted.org/packages/98/d2/6fa19239ff1ab072af40ebf339acd91fb97f34617c2ee625b8e34bf42393/gevent-websocket-0.10.1.tar.gz#sha256=7eaef32968290c9121f7c35b973e2cc302ffb076d018c9068d2f5ca8b2d85fb0 Best match: gevent websocket-0.10.1 ```...

I was able to work around this issue by installing gevent and friends within the CI, prior to building phoebe. The tests are now passing on linux, but failing on...

Superseded by #796.