-
Notifications
You must be signed in to change notification settings - Fork 240
pythonista>=3.4/py>=3.10: Refactoring, removing deprecated requirements, updating for
#524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
py>=3.10pythonista>=3.4 / py>=3.10 Refactoring, removing deprecated requirements, updating for
pythonista>=3.4 / py>=3.10 Refactoring, removing deprecated requirements, updating for pythonista>=3.4/py>=3.10: Refactoring, removing deprecated requirements, updating for
|
Please rebase on the current |
04e5e3f to
c4b4aa6
Compare
Done |
|
Can you please pull in the changes to
|
|
|
Please add
|
|
Do you use the tools |
c47c414 to
413b0d0
Compare
I use |
Done |
|
uv tool install pre-commit
pre-commit install
pre-commit run --all-files |
4012739 to
6636e15
Compare
|
@cclauss for some reason stacks on but pbtest -h on pytonista works |
|
I think it is getting hung up on the next file which is EDIT: Confirmed at https://github.com/ywangd/stash/pull/524/commits |
* if no scripts found in BIN_PATH will search in `site-packages/bin` * updated scripts matching logics, now able to find console-scripts installed with `pip` in `site-packages/bin` even with NON-`.py` extension * check python syntax with ast.parse() for non NON-`.py` files (maybe blacklist needed) * added `site-packages/bin` scripts completions (by checks only first 100 NON-`.py` files, to take < 1 second) * avoid the KeyboardInterrupt error in Pythonista 3.4..3.5: fix from ywangd#499
… compatible with Pythonista 3.4 or higher. * Removed all Python 2 patches * Removed deprecated wheels support. StaSh now uses a standard pip approach for installing Python wheels * The StaSh python alias has been set to python3 since Python 2 is no longer supported. * The man page_5.txt file has been updated to reflect the end of Python 2 support.
…miko` * Patched `time.clock()` (required by Crypto) * Allow patch undefined attributes * Apply patch to `bin/ssh.py` * Apply patch to `bin/ssh-keygen.py`
httpserver.py update and fixes
diff.py update and fixes
… `pip` (#14) pip.py update and fixes (resolving packages installation path)
* wc.py update and fixes * сut.py update and fixes
…ndline utility) (#16)
|
I just rebased this PR onto master |
P.S.: I already said I need a help with testing and porting, I'll be glad to see if someone will contribute |
|
If I remember correctly, there was a pull request with a python 3 compatible git implementation. Either the pull request is still there or it might be merged into the dev branch already.On 1. Sep 2025, at 10:15, Dmytro Yaroshenko notifications-at-github.com |github-fschaeckermann| ***@***.***> wrote:o-murphy left a comment (ywangd/stash#524)
@sloanlance
I guess I fixed it
git is not working now cause of lots of incompatible things I did not resolved yet.
The dulwich directly works as a cli tool, just install it with pip pip install dulwich, then run dulwich
And actualy I don't think it should be resolved in current PR, it is already massive
P.S.: I already said I need a help with testing and porting, I'll be glad to see if someone will contribute
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because your review was requested.Message ID: ***@***.***>
|
This branch was never be the git implementation update. It was created to resolve incompatibility of the stash itself with the newest Pythonista and Python. This branch removes deprecated support and compatibility layer for py2 (lib2to3 and six). It fixes most of commands and core issues to make it working on py3. For now git command not yet updated. And I have not anough time to complete git porting. The list of updated and tested commands are in the first post in this PR discussion. My proposal is making git command realisation not as much bounded with |
|
@bennr01 This repo has a |
looks like a sollution, one thing is needed is py2 guard |

Important
This PR does not offer backward compatibility with py2! However, it resolves problems for many commands. Possibly we
have to remove py2 support
Install to test using this command
WIP: updating to py3, removing deprecated requirements
pipapproach for installing Python wheelssiximp(replaced withimportlib)build-system
pip?__main__.pyRefactored entry point o-murphy/stash#1features
site-packages/binconsole-scriptssite-packages/binconsole-scripts support o-murphy/stash#3Updating core
corelaunch_stashgetstash__main__o-murphy#1__main__.pyUpdating system/
dummyconsoledummyobjc_utilshcommonshhistoryshioshiowrappershparsersshruntimeshscreensshstreamsshthreadsshureactionproxyshui/__init__shui/baseshui/dummyuishui/pythonistauishui/stubuishui/tkuiUpdating lib/
Updating bin/
aliascatcdclearcowsaycpcryptpyaes-whlcurlcutdiffdropbox_setupdueasy_configpinstashcommandechoeditexitfgfindftpservergcighgitdulwichfrompypigrepheadhttpserverjobskilllattelnlogoutlsmailmanmcmd5summkdirmonkeylordmoremountmvopeninpbcopypbpastepingpinstashpippipinstallation from bootstrap.pypa.ioprintenvprinthexptinstallerpwdpythonpython3python3quicklookrmrmdirscpselfupdatesha1sumsha256sumsortsourcesqlitesshssh-keygenstashconftailtartelnettelnetlibwithstandard-telnetlibtouchtreeumountuniqunzipversionwcwebviewerwgetwhatiswhichwolxargszipKnown issues:
pwdnot in Pythonista builtinsos.system()fsirequiredropboxinstalled and it is not optionalbin/telnetshould be reimplemented withtelnetlib3orExscriptand asyncio in futureFAILED tests/system/test_threads.py::ThreadsTests::test_101 - AssertionError: output not identical assert '[stash]$ sleeping ... 0\n[stash]$ sleeping ... 1\n' == '[stash]$ [stash]$ sleeping ... 0\nsleeping ... 1\n'Cryptois outdated #544pipcan not build packages on installation, even if it pure-python. It allows only.whl. The possible fix for it is implementing subprocess patches for Py3pipcan't remove entry-points from~/Documents/binon package uninstalling, it's due to absent possibility to add--prefixpath to PYTHONPATH globally, so the packages tree is not match PEP-370