Replies: 8 comments 10 replies
-
what about Django? I feel like we got a lot of requests for Django specifically, both in person and online. #168 #211
Agreed, tho I think we should aim for near-perfect conformance for anything related to generics/callables. In my mind there's a list of "tricky" problems that we should solve before v1. This is similar to the list of big features we were talking about during planning. Happy to hear suggestions for anything to add/deprioritize:
|
Beta Was this translation helpful? Give feedback.
-
|
good environment/project support (venv, uv, ide configs, PYTHONPATH) perhaps |
Beta Was this translation helpful? Give feedback.
-
|
I would argue that type checking bugs that prevent go to definition should be prioritized over bugs that yield errors, but do not impact IDE navigation |
Beta Was this translation helpful? Give feedback.
-
|
per #544 it sounds like rename is a must-have for the IDE. I think we should support everything in #344 before calling it v1 |
Beta Was this translation helpful? Give feedback.
-
|
What do we think about GitHub first development once we are V1? |
Beta Was this translation helpful? Give feedback.
-
|
Here is another spicy one... type errors are off by default for VSCode unless there is a pyrefly configuration present. We could prompt an |
Beta Was this translation helpful? Give feedback.
-
|
AFAIK Pyrefly doesn't support type comments for type hints like others do, such as Pylance. Although this isn't an issue for those using Python 3.5+, type comments are really helpful for me and possibly others who struggle with projects in older versions of Python. Pyrefly does offer great performance improvements, which is why I switched to it. However, the lack of support for type comments is really a pain point for me, and I hope Pyrefly consider adding this feature🙏 Some examples, more info here a = 1 # type: int
def foo(a, b): # type: (int, int) -> int
return a + b |
Beta Was this translation helpful? Give feedback.
-
|
Quick update for anyone who's following along: we're working toward a beta release later this year (V1 will come after beta). Milestone here: https://github.com/facebook/pyrefly/milestone/4. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Starting a discussion about what should be in Pyrefly's V1 Release. Here's a list of ideas we kicked around in yesterday's eng sync:
My thoughts:
Thoughts? Is there anything I missed that folks want to see in V1?
Beta Was this translation helpful? Give feedback.
All reactions