Skip to content
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.

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

.then execution of actions following a future's completion #76853

Closed
dancollins34 mannequin opened this issue Jan 26, 2018 · 4 comments
Closed

.then execution of actions following a future's completion #76853

dancollins34 mannequin opened this issue Jan 26, 2018 · 4 comments
Labels
3.8 only security fixes topic-asyncio type-feature A feature request or enhancement

Comments

@dancollins34
Copy link
Mannequin

dancollins34 mannequin commented Jan 26, 2018

BPO 32672
Nosy @bitdancer, @asvetlov, @1st1, @dancollins34
PRs
  • Fix version in AppVeyor #5535
  • bpo-32672: Add then execution for chaining python futures issue #5335
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2018-05-28.20:04:09.589>
    created_at = <Date 2018-01-26.04:04:24.992>
    labels = ['type-feature', '3.8', 'expert-asyncio']
    title = ".then execution of actions following a future's completion"
    updated_at = <Date 2018-05-28.20:04:09.588>
    user = 'https://github.com/dancollins34'

    bugs.python.org fields:

    activity = <Date 2018-05-28.20:04:09.588>
    actor = 'yselivanov'
    assignee = 'none'
    closed = True
    closed_date = <Date 2018-05-28.20:04:09.589>
    closer = 'yselivanov'
    components = ['asyncio']
    creation = <Date 2018-01-26.04:04:24.992>
    creator = 'dancollins34'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 32672
    keywords = ['patch']
    message_count = 4.0
    messages = ['310730', '310731', '310733', '317703']
    nosy_count = 4.0
    nosy_names = ['r.david.murray', 'asvetlov', 'yselivanov', 'dancollins34']
    pr_nums = ['5535', '5335']
    priority = 'normal'
    resolution = 'rejected'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue32672'
    versions = ['Python 3.8']

    @dancollins34
    Copy link
    Mannequin Author

    dancollins34 mannequin commented Jan 26, 2018

    To my knowledge, python currently has no capability to chain future execution, requiring another future to begin executing with the result from the first.

    I have submitted a pr to enable this functionality with a .then(self, fn) method on the concurrent.futures.Future object.

    -dancollins34

    @dancollins34 dancollins34 mannequin added interpreter-core (Objects, Python, Grammar, and Parser dirs) 3.7 (EOL) end of life labels Jan 26, 2018
    @bitdancer
    Copy link
    Member

    I think this requires a discussion on the python-ideas mailing list, since API changes to Future need consideration in the asyncio context as well.

    @bitdancer bitdancer added stdlib Python modules in the Lib dir 3.8 only security fixes type-feature A feature request or enhancement and removed interpreter-core (Objects, Python, Grammar, and Parser dirs) 3.7 (EOL) end of life labels Jan 26, 2018
    @dancollins34
    Copy link
    Mannequin Author

    dancollins34 mannequin commented Jan 26, 2018

    Okay, I'll post something.

    @1st1
    Copy link
    Member

    1st1 commented May 25, 2018

    Closing this one. I don't see us adding Future.then. Feel free to discuss on the MLs.

    @1st1 1st1 added topic-asyncio and removed stdlib Python modules in the Lib dir labels May 25, 2018
    @1st1 1st1 closed this as completed May 28, 2018
    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    3.8 only security fixes topic-asyncio type-feature A feature request or enhancement
    Projects
    None yet
    Development

    No branches or pull requests

    2 participants