Update environment.yml

[erogluorhan]

Update environment.yml to:

• Revert installation of uxarray from the main branch to conda relases
• Remove jupyter_server per this

[github-actions]

👋 Thanks for opening this PR! The Cookbook will be automatically built with GitHub Actions. To see the status of your deployment, click below.
🔍 Git commit SHA: eb18f3e
✅ Deployment Preview URL: https://ProjectPythia.github.io/unstructured-grid-viz-cookbook/_preview/12

[erogluorhan]

Hey @philipc2 you may want to see the error in the book build process as it maybe related to April's release

[philipc2]

Hey @philipc2 you may want to see the error in the book build process as it maybe related to April's release

Taking a look at it!

[philipc2]

Previously, we were raising a warning when the user attending to do uxds.plot(), however now we are raising an exception with a more detailed

Before

After

I wonder what the correct way to show off an exception is in a notebook without it breaking the build?

[erogluorhan]

Previously, we were raising a warning when the user attending to do uxds.plot(), however now we are raising an exception with a more detailed

Before

After

I wonder what the correct way to show off an exception is in a notebook without it breaking the build?

Got it!

I don't know if there is a correct one among multiple ways to do this. One immediate way would be to put a try-catch block into that cell (don't know if it would look elegant though), and print something out of the cell in the catch to show there was an exception.

[philipc2]

Previously, we were raising a warning when the user attending to do uxds.plot(), however now we are raising an exception with a more detailed

Before

After

I wonder what the correct way to show off an exception is in a notebook without it breaking the build?

Got it!

I don't know if there is a correct one among multiple ways to do this. One immediate way would be to put a try-catch block into that cell (don't know if it would look elegant though), and print something out of the cell in the catch to show there was an exception.

Yeah, I thought of the try-catch, but from a readers perspective it might be confusing.

Maybe we don't need to run uxds.plot() and we could just document it in the markdown?

[erogluorhan]

Yeah, I thought of the try-catch, but from a readers perspective it might be confusing.

Maybe we don't need to run uxds.plot() and we could just document it in the markdown?

How about commenting that out and putting a comment before it to say running that line would show the exception? If this makes sense, I can add it to this PR

[philipc2]

Yeah, I thought of the try-catch, but from a readers perspective it might be confusing.
Maybe we don't need to run uxds.plot() and we could just document it in the markdown?

How about commenting that out and putting a comment before it to say running that line would show the exception? If this makes sense, I can add it to this PR

That sounds like a great idea, go ahead and include it in this PR!

[erogluorhan]

Yeah, I thought of the try-catch, but from a readers perspective it might be confusing.
Maybe we don't need to run uxds.plot() and we could just document it in the markdown?

How about commenting that out and putting a comment before it to say running that line would show the exception? If this makes sense, I can add it to this PR

That sounds like a great idea, go ahead and include it in this PR!

Done! Feel free to give it a review now that we got the build fixed (Added two more commits to sort the bullet points in the Why UXarray? part, but that's it, there will not be any more commits I believe)

[philipc2]

All looks good!