Live data from Hacker News

Helium: Lighter Web Automation with Python

github.com

51–53 of 53 posts

Re: Helium: Lighter Web Automation with Python

#51

Importing * is universally discouraged by most Python linters and best practice docs. You can always "import helium as h" if you're looking to type less. This looks largely like common workarounds that most people will write using Python-based browser automation. Most of the time, we accept that those capabilities aren't there by default because they are not explicit enough and can result in bugs and undefined behavi…

[dead]

Re: Helium: Lighter Web Automation with Python

#52
post #50

That looks useful. How does it know which box is the user field? Just read label and assume the one below that or to the right of the label?

Pretty much, yes. And if there are multiple, then it uses the matching element closest to the last one it interacted with. Much like a human.

Re: Helium: Lighter Web Automation with Python

#53
post #47

Selenium project founder here. (Hi!) Thanks for all your work on this project. Lots of negativity around here these days, but just wanted to say thanks. The functional style of Helium's API reminds me a lot of Selenium's original API when it was 100% JavaScript (aka Selenium 1 aka Selenium Core) back in 2004. (Functional style: "method(thing)" vs object oriented style: "thing.method()") We mostly abandoned the functi…

UFCS is great. I really wish more languages would support something similar, although both pipe operators (thing |> function1 |> function2) or Rust's proposal for thing.(function) seem to also satisfy the syntactic ideal.
Post reply on HN