I think those limitations also lead to a lot of creativity. Good music is often made under severe constraint.

I agree, it can be a boon to creativity, but it’s precisely because the UI is bad (limited).

If by running models you mean just the inference phase, then even today you can run large family of ML models on commodity hardware (with some elbow grease, of course). The training phase is generally the one not easily replicated by non-corporations.

Exactly, I mostly write in Latex and one-sentence-per-line makes so much sense for that.

> When printing tracebacks, the interpreter will now point to the exact expression that caused the error instead of just the line. For example:

  Traceback (most recent call last):
    File "distance.py", line 11, in <module>
      print(manhattan_distance(p1, p2))
            ^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "distance.py", line 6, in manhattan_distance
      return abs(point_1.x - point_2.x) + abs(point_1.y - point_2.y)
                             ^^^^^^^^^
  AttributeError: 'NoneType' object has no attribute 'x'

This is such a great quality of life improvement.

This is an INCREDIBLE improvement. I'm so excited for it for myself, and I think it will also do wonders for getting new programmers comfortable with the language. Seeing exactly where in the line your error is, is amazing! IMO this 100% cements Python as the single most newbie-friendly language, if there was any question before now (or at least, before the release of 3.11).

You can already get this information for Python 3.6+ with https://friendly-traceback.github.io/docs/index.html

I already move code into separate lines since this is currently missing. This is great indeed. (Although that might still make sense for debugging)

It would sure be great if they made it easier to break to the debugger in case of an unhandled exception, like (setq debug-on-error t) in Emacs Lisp.

This can be done in some IDEs. Although it can get confusimg if you’re working in an app framework that does some sort of catch-all exception handling.

Yeah it seems to me that regular Python should be able to do it though.

Well if you like this, you are going to love 3.10 due for tomortow, because it's packed with a lot of error message improvements.

Everybody talks about the pattern matching, but I'm excited about this. I'm going to upgrade ASAP just so for it.

Oh wow, I completely missed this in the release notes, probably due to not carefully reading them since earlier versions. This is amazing!

Really wish they'd just go and add a way to replace better-exceptions[0]. I don't use it anymore and thus don't really like to maintain it these days, and would love to see it in mainline.

[0] https://GitHub.com/qix-/better-exceptions

This can be found at [1].

[1] https://docs.python.org/3.11/whatsnew/3.11.html

Currently the only way to sign up for a personal account is through google. Is there another way that I am missing, or are there any plans to provide email based signups in the future?

(Replay engineer) Google is currently the only way unfortunately. We wanted to support secure logins at launch, with SSO and Multi-factor Authentication, and focus most of our efforts on the core product. As a result we just went with Google for launch.

We don't currently have any plans to add additional authentication mechanisms but we've heard this feedback from a couple folks and we'll sit down to prioritize it after the excitement of launch has died down. Sorry about that!

Even for Google logins, would you consider using a token-based authentication system (like Spotify, Postman, etc. do)... i.e., your default browser opens, Google logs you in there (or you already are), and that sends a backend auth token to your service to connect your Google and Replay accounts.

I would like to try your product, but am wary of typing in my Google credentials into an unknown, black-box browser. It's too easy to MITM, especially if someone redistributes a copy with a keylogger shimmed in.

The token-based auth means you can still log in with Google but never have to share your Google password with the proprietary Replay browser. Probably many of the multi-login vendors support something similar already if you don't want to deal with it yourself.

Thanks for the update. I had a feeling that this might have been the case due to the launch crunch and it's perfectly understandable. Really excited for the future of this project!

It's not even a niche use cases, many times IT teams would suggest deleting the cookies and cache for a specific site to overcome common login issues.

I am looking forward to performance improvements. It would be great if the core window services were optimized to use less resources to improve the windows experience on less impressive hardware.

> I don’t care about Kubernetes, but someone might read this post and decide that it is a good idea to “simplify” an existing project by rewriting it in 17000 lines bash script.

I think the 17kloc would discourage that kind of thinking.

Great project! I've had success using camelot-py (https://camelot-py.readthedocs.io) to extract tabular data from PDFs (for images, I use imagemagick to convert those to PDF). If your table has borders the default method (lattice) works quite well. For non-bordered table there is the option to use 'stream' option but usually requires bit more preprocessing to get usable results.

Hey! Camelot maintainer here. You can check out this doc for details on how Camelot extracts tables from PDFs: https://camelot-py.readthedocs.io/en/master/user/how-it-work...

As pointed out in this thread, right now it only works with text-based PDFs. But there's a PR[1] which will add OCR support (using EasyOCR) for image-based PDFs in some time.

[1] https://github.com/camelot-dev/camelot/pull/209

From the link: "Camelot only works with text-based PDFs and not scanned documents." If you have character data, using it is almost always going to be more accurate than OCR.

I don't know how OP uses it with images converted to PDFs though, as that would be just like a scan, and ImageMagick doesn't do OCR as far as I can tell.

It uses pytesseract and Open-CV, so there is image processing.

Looks like it's a bit in-progress: https://github.com/camelot-dev/camelot/pull/209

"Update docs" isn't checked, and that's what I was going on.

Yes I need to work on that PR, haven't been getting a lot of free time these days. It adds OCR support using EasyOCR, which I found on HN some time ago!

I am considering building a PC for programming and am genuinely curious if WSL2 can be considered a replacement for dual booting Linux and Windows? I am currently rocking a dual boot system (with legacy bios) and haven't had any issues so far.

It's pretty close. Big pain point for me still is that running an IDE from Windows and accessing the Linux FS is not quite as snappy as native-Linux (I use IntelliJ). So for now I still dual-boot.

This is apparently being worked on... in the future I will be able to run the IDE inside WSL and it will bridge X11/Wayland to Windows.

If you can try using Visual Studio Code, with their remote plugins. One of the remote plugins is for wsl2 and it works great.

That means that VSC installs language server inside the wsl2 environment, I use it at home for my rust/python development and can't tell the difference.