Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add handling of asyncio coroutines.#162

Open
apollovy wants to merge 1 commit intopythonprofilers:masterfrom
apollovy:master
Open

Add handling of asyncio coroutines.#162
apollovy wants to merge 1 commit intopythonprofilers:masterfrom
apollovy:master

Conversation

@apollovy
Copy link

Hi.
This patch works for current versions of python, but breaks <3.3 whereyield from is a syntax error and returning from generatior is not allowed.
I will just leave it here in case somebody would want to use this project in async world.
By now I don't see an easy way to deal with the situation except that making a dependency from tornado in 2.7 (and maybe 2.6) and use their machinery for coroutines. But by now I doubt it's worth spending a time on it 🤗
Fixes#161

Copy link
Collaborator

@astrojuanluastrojuanlu left a comment

Choose a reason for hiding this comment

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

Hi! We just made some infrastructure changes that conflict with your PR. Would you mind rebasing and trying again? Also, adding some tests would be nice :)

from distutils.core import setup
import setuptools

import memory_profiler
Copy link
Collaborator

Choose a reason for hiding this comment

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

The method to extract the version was changed.

license='BSD'

license='BSD',
install_requires=['asyncio>=3.4.3'] if sys.version_info < (3, 4) else [],
Copy link
Collaborator

Choose a reason for hiding this comment

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

What about using PEP 426 markers instead?https://blog.ionelmc.ro/presentations/packaging/#slide:25

@OleksaVasylenko
Copy link

@apollovy Hi! Are you going to finish that? That would be a great benefit.

@apollovy
Copy link
Author

apollovy commentedSep 21, 2018 via email

Hi. I believe not in the nearest future at least: no time or any plansabout it. It just works for me, so I'm using it from my fork and that's it.пт, 21 сент. 2018 г., 14:12 Oleksa Vasylenko <notifications@github.com>:
@apollovy <https://github.com/apollovy> Hi! Are you going to finish that? That would be a great benefit. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#162 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABmCLyL6lszyFJWj6pMPYwqKCb1Sfn1xks5udMmLgaJpZM4PpAME> .

@astrojuanlu
Copy link
Collaborator

@OleksaVasylenko if you want to take over, you could do like this on a local memory_profiler checkout:

$ git checkout -b apollovy-master e2a97b9$ git rebase upstream master  # Fix conflicts$ git pull https://github.com/apollovy/memory_profiler.git master

and we can continue the review from there. Thanks!

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@astrojuanluastrojuanluastrojuanlu requested changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@apollovy@OleksaVasylenko@astrojuanlu

[8]ページ先頭

©2009-2026 Movatter.jp