| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
support for incognito / private browsing
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
Sorry, something went wrong.
default value set in base class
Sorry, something went wrong.
removed %incognito since using %action for the implementation
|
tested on linux with
opera opens automatically with a private tab. |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks a lot for the feature suggestion.
I will take another look when you will remove unrelated changes :)
Sorry, something went wrong.
…7osoHj.rst Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
There was a problem hiding this comment.
Please, also add tests for browsers that support it. And a doc note about this new feature.
Thank you for the quick response! 👍
Sorry, something went wrong.
| elif o == '-t': new_win = 2 | ||
| elif o == "-i": | ||
| new_win = 3 | ||
| elif o == "-b": |
There was a problem hiding this comment.
Why do we have -b and -l added? I am not opposed to this, but again: this feature is not related.
If you feel like adding this feature is a good idea (it looks like it might be), please open a new issue: explain the use-case and the "why".
But, let's keep this PR simple: only incognito mode.
Sorry, something went wrong.
There was a problem hiding this comment.
it is related to the cmdline interface when webbroser main() func is called.
they belong also to the newly added incognito method.
therefore it is not a new feature from my perspective.
Sorry, something went wrong.
There was a problem hiding this comment.
This is not resolved at all. These are separate new additions.
Sorry, something went wrong.
There was a problem hiding this comment.
Agreed
Sorry, something went wrong.
There was a problem hiding this comment.
We do appreciate your contribution here!
As the PR author, you are in the best place to address the review by removing the code added to support --browser.
That can be discussed in a separate issue. But if you don’t have the time, then someone else could complete the PR.
Sorry, something went wrong.
There was a problem hiding this comment.
for me this is a migration topic. the experts do know better what to do here. myself i dont see here in the working loop since i dont have this detailed knowledge of what being best on master code baseline
Sorry, something went wrong.
There was a problem hiding this comment.
Sorry, I don’t understand «migration». There are clear requests to remove some code that was added, to keep this PR focused on one thing. If you don’t want to pursue it, then someone else will have to volunteer.
Sorry, something went wrong.
|
i would suggest that someone else will do auto formatting with black (PEP08) |
Sorry, something went wrong.
Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
|
i followed the approach of the given tests under Lib/test/test_webbrowser.py and added some more for parameter checking (as far i understood that is how it works). but since even the original tests i can not run here on my local machine (3 are failing) i created now a gist rather than releasing it. https://gist.github.com/kr-g/95a06df8f0fcf77ad10474724350e921 |
Sorry, something went wrong.
There was a problem hiding this comment.
Remove stuff unrelated to the issue.
Sorry, something went wrong.
| elif o == '-t': new_win = 2 | ||
| elif o == "-i": | ||
| new_win = 3 | ||
| elif o == "-b": |
There was a problem hiding this comment.
This is not resolved at all. These are separate new additions.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
I fetched the this PR and I made some changes, but now how can I make the PR on this PR ? |
Sorry, something went wrong.
gh-105983 merged contribution from amir for edge browser support
|
Thanks for the update! Some things still to do (I unresolved the relevant threads):
|
Sorry, something went wrong.
|
@kr-g There's not much point updating this branch from main unless the unresolved items are addressed. |
Sorry, something went wrong.
|
@kr-g As mentioned, there's no point updating this PR from main unless the other issues are going to be resolved. Otherwise we let's close this, and we can re-open it when those issues have been addressed. |
Sorry, something went wrong.
i use the branch - therefore i merge from time to time. |
Sorry, something went wrong.
but anyway good to know the intention to kick me out of my own code. |
Sorry, something went wrong.
|
Hi @kr-g, we have no intention of kicking you out of your own code :) However, by keeping a PR open against the CPython repo, you are indicating that this patch is something you are actively seeking to be merged into the main branch, and would like CPython maintainers to engage with. If you are not interested in addressing the comments of the reviewers here, that is your right, but you cannot expect for this PR to be kept open indefinitely. If the PR is closed, the branch will not be deleted, and you will be able to continue using it locally. You will not be kicked out of your own code in any way. However, the PR will no longer show up as an active, open PR against the CPython repo that maintainers should engage with and attempt to review. It sounds as though you are currently uninterested in addressing the comments of the reviewers here, so I'm going to close this. If I'm incorrect, and you are still interested in having this patch merged into the CPython main branch, please let us know, and we can reopen the PR :) |
Sorry, something went wrong.
|
i already said it some months ago that i see the "experts" here in charge to take over those topics because from my point of view thats an integration (or migration) issue to split the PR or rename a feature. i m not an expert and dont know what fits best on cpython baseline. but somehow this turns out to be ... well anyone can read and have an own idea about it. |
Sorry, something went wrong.
|
CPython is an open-source project maintained by volunteers, who have limited time to help PRs make it over the finish line. I'm afraid it's the responsibility of the author of the PR to ensure that it's of a quality suitable to be merged, not the responsibility of the CPython core developers. We've given you advice on the changes that would be required to get this into a state where it could be merged; in this instance, that's as much as we can do. |
Sorry, something went wrong.
|
since i have doubled the webbrowser code already in my own project that all is not of importance to me. in case it comes somewhere in time i dont bother. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Support incognito / private browsing.