Selene

Latest version: v1.0.2

Safety actively analyzes 685670 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 16

2.0.0a21

- fixed hooks for entities created via entity.with_(Config(...))

2.0.0a20

- Fixed UnicodeEncodeError: 'charmap' codec
- thanks to [PR-197](https://github.com/yashaka/selene/pull/197) from ak40u

2.0.0a19

- removed deprecation from shared.config.counter and reports_folder
- removed backports.functools-lru-cache from project dependencies
- removed six from explicit project dependencies
- removed selene.version.py (moved version number to selene.__init__.__version__)
- deprecated: by.be_following_sibling, be_parent, be_first_child
- use xpath explicitly to not hide complexity in workaround
- yet you can create you own xpath helpers to to show that you are using xpath but in a more readable style
- like: x.following_sibling, ...
- the only exception is by.text
- it uses xpath under the hood, but so complicated that no way to use it explicitly :)
- removed warning from `collection.first`
- it's nevertheless useless.
- `first` is the one of things that breaks your code when migrating to 2.*
- after migration, just find&replace every `.first()` to `.first`, and that's it:)

2.0.0a18

- deprecated finally `send_keys`, added `press(*keys)` instead
- use `type` for 'typing text', use `press` or `press_enter` & co for 'pressing keys'
- removed s, ss from selene.support.shared (were added by mistake in a17)
- yet unsure... maybe it was a good idea... to keep s, ss in shared.__init__.py too... let's think on this more...
- removed selene.api.base and selene.api.shared from distribution
- even selene.api is not needed anymore... let's not use it...
- it was needed in the past for * style imports,
- but nevertheless it's a bad practice to do so...
- updated readme and project long description for pypy

2.0.0a17

- deprecated selene.config, use `from selene.support.shared import config` instead
- where you also can find shared browser: `from selene.support.shared import browser, config`
- you also can go the minimalistic way with the only `browser` import:
- `from selene.support.shared import browser`
- `browser.config.browser_name = 'firefox'`
- `browser.config.base_url= 'https://google.com'`
- `browser.config.timeout = 2`
- `browser.open('/ncr/')`
- deprecated selene.support.jquery_style_selectors
- because it's technically is based on selene.support.shared.*, so was structured incorrectly
- use selene.support.shared.jquery_style instead
- separate core from shared selene api in selene.*
- now to get shared browser or config you have to import them explicitly from selene.support.shared
- added some base docs into selene.__init__

2.0.0a16

- fixed absent screenshots for customized elements through with_
- e.g. in `browser.element(...).with_(timeout=...).should(be.visible)`
- as impl: moved main auto-saving screens/page_source logic to SharedConfig
- deprecated latest_* methods in Browser in favour of last_*
- added experimental syntax for ignore_case in:
- `browser.element(...).should(have.attribute('foo').value('bar', ignore_case=True)`
- `browser.element(...).should(have.attribute('foo').value_containing('bar', ignore_case=True)`
- open points:
- while it's more or less ok here... but is it ok in:
- `browser.all(...).should(have.texts('a', 'b', 'c', ignore_case=True')`
- or better?
- `browser.element(...).should(have.texts_ignoring_case('a', 'b', 'c')`
- taking into account that one day there might be an ask for:
- `browser.all(...).should(have.texts('a', 'b', 'c', in_any_order=True)`
- or
- `browser.all(...).should(have.texts_in_any_order('a', 'b', 'c')`
- seems like better to have options over predefined names... to combine them whatever you like
- but what then to do with conditions like value_containing? move _containing to option to?
- `browser.element(...).should(have.value('a', contained=True, ignore_case=True')`
- ooo, and this is also technically possible:
- `browser.element(...).should(have.value('a').contained.ignoring_case)`

Page 9 of 16

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.