| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
As discussed in gitter, I think we should fix this properly. OTOH, happy for this to go in when the build passes.... |
Sorry, something went wrong.
|
If we want this in the 3.3 docs, then I'm happy to update. If we're actually going to fix properly for 3.4, then there's no point in putting this in. |
Sorry, something went wrong.
|
I think it'd be good to get this in because I have a feeling we won't be able to re-engineer Locators and Formatters by 3.4 (though who knows! Where there is a will there is a way). |
Sorry, something went wrong.
The note about not sharing `Locator` instances should be more prominent than hiding in the base class docs, which most users have no need to examine.
|
Should this be milestoned for 3.3-doc? |
Sorry, something went wrong.
|
I don't think there's anything else this needs... |
Sorry, something went wrong.
|
Seems fine to me. |
Sorry, something went wrong.
|
Something went wrong ... Please have a look at my logs. It seem that the branch you are trying to backport to does not exists. |
Sorry, something went wrong.
|
@meeseeksdev backport to v3.3.3-doc |
Sorry, something went wrong.
…002-on-v3.3.3-doc Backport PR #19002 on branch v3.3.3-doc (DOC: Add note about locators at top of ticker docs)
|
Two other thoughts in this space:
|
Sorry, something went wrong.
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Summary
The note about not sharing Locator instances should be more prominent than hiding in the base class docs, which most users have no need to examine (since they'll use one of many subclasses 99% of the time).
I opted not to add anything to the text_intro.py tutorial, but I'm open to doing so if someone has suggestions on the right level of detail for that.
PR Checklist