Skip to content

Conversation

@AntonNI8
Copy link
Contributor

@AntonNI8 AntonNI8 commented Oct 31, 2025

Before submitting

Please complete the following checklist when submitting a PR:

  • Ensure that your tutorial executes correctly, and conforms to the
    guidelines specified in the README.

  • Remember to do a grammar check of the content you include.

  • All tutorials conform to
    PEP8 standards.
    To auto format files, simply pip install black, and then
    run black -l 100 path/to/file.py.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.


Title:

Summary:

Relevant references:

Possible Drawbacks:

Related GitHub Issues:


If you are writing a demonstration, please answer these questions to facilitate the marketing process.

  • GOALS — Why are we working on this now?

    Eg. Promote a new PL feature or show a PL implementation of a recent paper.

  • AUDIENCE — Who is this for?

    Eg. Chemistry researchers, PL educators, beginners in quantum computing.

  • KEYWORDS — What words should be included in the marketing post?

  • Which of the following types of documentation is most similar to your file?
    (more details here)

  • Tutorial
  • Demo
  • How-to

@github-actions
Copy link

👋 Hey, looks like you've updated some demos!

🐘 Don't forget to update the dateOfLastModification in the associated metadata files so your changes are reflected in Glass Onion (search and recommendations).

Please hide this comment once the field(s) are updated. Thanks!

@AntonNI8 AntonNI8 changed the base branch from master to filter-fix November 14, 2025 22:26
doctorperceptron added a commit that referenced this pull request Nov 17, 2025
After the update to Sphinx, Sphinx Gallery now outputs a different
format for generated code blocks, where the code block is now part of an
entirely separate element and no longer nested in `rst-class` directive.
This PR adds a fix to be able to handle both the new and old
`sphx-glr-script-out` formats. It has been tested on #1592 .
Base automatically changed from filter-fix to master November 17, 2025 14:23
@github-actions
Copy link

github-actions bot commented Nov 17, 2025

Your preview is ready 🎉!

You can view your changes here

Deployed at: 2026-01-09 20:58:47 UTC

@Jaybsoni Jaybsoni requested a review from josh146 December 15, 2025 15:22
Copy link
Member

@josh146 josh146 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @Jaybsoni @AntonNI8, this is fantastic 💪

Clear, concise, and tells a compelling story.

Is the plan to merge it into dev, and have it go live for the next PL release?

@PennyLaneAI PennyLaneAI deleted a comment from josh146 Dec 23, 2025
Copy link
Contributor

@ddhawan11 ddhawan11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @AntonNI8. Looks good overall, a few typos and stylistic choices.

Copy link
Contributor

@obliviateandsurrender obliviateandsurrender left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just a few minor optional comments! 🚀

@ddhawan11 ddhawan11 self-requested a review January 9, 2026 20:51
Copy link
Contributor

@ddhawan11 ddhawan11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @AntonNI8 and @Jaybsoni. Looks good!
Please remove the citations before merging.

@AntonNI8 AntonNI8 merged commit 2c8c44c into dev Jan 9, 2026
12 checks passed
@AntonNI8 AntonNI8 deleted the re_howto branch January 9, 2026 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants