8000 Better error handling for invalid children by pelme · Pull Request #56 · pelme/htpy · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Better error handling for invalid children #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Sep 12, 2024
Merged

Better error handling for invalid children #56

merged 1 commit into from
Sep 12, 2024

Conversation

pelme
Copy link
Owner
@pelme pelme commented Sep 9, 2024

Related #49 and #55 but this PR fixes error handling for children.

@pelme pelme force-pushed the better-errors-children branch from bb5d7a5 to 2ae684b Compare September 9, 2024 19:07
@pelme pelme marked this pull request as ready for review September 9, 2024 19:10
@pelme pelme changed the title WIP: Better error handling for invalid children Better error handling for invalid children Sep 9, 2024
@pelme pelme force-pushed the better-errors-children branch 3 times, most recently from 873cb79 to ac3aca4 Compare September 12, 2024 19:03
@pelme
Better error handling for invalid children.
9f16b77 
Validate children directly when possible.
@pelme pelme force-pushed the better-errors-children branch from ac3aca4 to 9f16b77 Compare September 12, 2024 19:04
@pelme pelme merged commit 909ecb8 into main Sep 12, 2024
13 checks passed
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
7af678e 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
@pelme pelme mentioned this pull request Dec 15, 2024
Merged
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
aec53b0 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
b391be8 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
ea92267 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
68f97d5 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
8c15d3a 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
8bccab7 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
876d6f8 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
66ab3b7 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
5c1e27d 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
e91370e 
Previously there were checks for generators specifically. We also support
one-off iterables that are not based on generators such as itertools.chain()
or any non-generator based object that implements __next__().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
fb30eb6 
Previously there were checks for generators specifically and not iterators in
general. We also support one-off iterators that are not based on generators such
as itertools.chain().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
142926d 
Previously there were checks for generators specifically and not iterators in
general. We also support one-off iterators that are not based on generators such
as itertools.chain().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
0e7372a 
Previously there were checks for generators specifically and not iterators in
general. We also support one-off iterators that are not based on generators such
as itertools.chain().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
f0d173d 
Previously there were checks for generators specifically and not iterators in
general. We also support one-off iterators that are not based on generators such
as itertools.chain().

This regression was introduced in #56.

Based on #71.
pelme added a commit that referenced this pull request Dec 15, 2024
@pelme
Make possible to use one-shot iterators as children nodes.
11bf4ff 
Previously there were checks for generators specifically and not iterators in
general. We also support one-off iterators that are not based on generators such
as itertools.chain().

This regression was introduced in #56.

Based on #71.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@pelme
0