Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

spacy.load() on python 3.12 with vscode #13263

Closed
lsmith77 opened this issue Jan 23, 2024 · 3 comments
Closed

spacy.load() on python 3.12 with vscode #13263

lsmith77 opened this issue Jan 23, 2024 · 3 comments
Labels
third-party Third-party packages and services

Comments

@lsmith77
Copy link

I think this is technically not a bug in this repo but it will likely affect other people too.

I have also found the same behavior in this carpedm20/emoji#280, which led to the creation of this ticket microsoft/debugpy#1496

How to reproduce the behaviour

Call spacy.load() using Python 3.12 when launching using VSCode.

Your Environment

  • Operating System: OSX
  • Python Version Used: 3.12.1
  • spaCy Version Used: 3.7
  • Environment Information:
@svlandeg svlandeg added the third-party Third-party packages and services label Jan 23, 2024
@svlandeg
Copy link
Member

Thanks for the report!

So basically the issue is that spacy.load is much slower with Python 3.12 in VSCode? But it's an upstream issue?

@lsmith77
Copy link
Author

Yeah that is what I suspect is the case. The issue is caused by large python files since Python 3.12 triggers an event for each line slowing the debugger down. They appear to be refactoring the VSCode to use some new 3.12 dedicated APIs.

In theory spacy could "fix" this by changing relevant files to put everything on a single line.

@svlandeg
Copy link
Member

Right, thanks for the additional explanation!

I don't think we'd want to adjust spaCy's core files to accomodate this "feature" by VSCode at this point in time, but let me move this to the discussion forum so we can keep track of this thread and keep the discussion open to anyone.

@explosion explosion locked and limited conversation to collaborators Jan 24, 2024
@svlandeg svlandeg converted this issue into discussion #13266 Jan 24, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
third-party Third-party packages and services
Projects
None yet
Development

No branches or pull requests

2 participants