| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Initially spotted since 'larg' was picked up by codespell as something possibly
to fix to become 'large'. But realized that it is just an inconsistency.
Had various uses:
❯ git grep '\*arg\>' | nl
1 paramiko/sftp_client.py: def _request(self, t, *arg):
2 paramiko/sftp_client.py: num = self._async_request(type(None), t, *arg)
3 paramiko/sftp_client.py: def _async_request(self, fileobj, t, *arg):
4 paramiko/sftp_server.py: def _response(self, request_number, t, *arg):
❯ git grep '\*largs\>' | nl
1 paramiko/sftp_server.py: *largs,
2 paramiko/sftp_server.py: self.server = sftp_si(server, *largs, **kwargs)
3 paramiko/sftp_si.py: def __init__(self, server, *largs, **kwargs):
4 paramiko/sftp_si.py: super().__init__(*largs, **kwargs)
❯ git grep '\*larg\>' | nl
1 paramiko/server.py: handler = handler_class(channel, name, self, *larg, **kwarg)
2 paramiko/transport.py: def set_subsystem_handler(self, name, handler, *larg, **kwarg):
in addition to more conventional
❯ git grep '\*args\>' | nl
1 paramiko/_winapi.py: super().__init__(*args)
2 paramiko/_winapi.py: def __init__(self, *args, **kwargs):
3 paramiko/_winapi.py: super().__init__(*args, **kwargs)
4 paramiko/auth_handler.py: def _log(self, *args):
5 paramiko/auth_handler.py: return self.transport._log(*args)
6 paramiko/channel.py: def _check(self, *args, **kwds):
7 paramiko/channel.py: return func(self, *args, **kwds)
8 paramiko/channel.py: def _log(self, level, msg, *args):
9 paramiko/channel.py: self.logger.log(level, "[chan " + self._name + "] " + msg, *args)
10 paramiko/sftp.py: def _log(self, level, msg, *args):
11 paramiko/sftp.py: self.logger.log(level, msg, *args)
12 paramiko/sftp_client.py: def _log(self, level, msg, *args):
13 paramiko/sftp_client.py: self._log(level, m, *args)
14 paramiko/transport.py: def _log(self, level, msg, *args):
15 paramiko/transport.py: self.logger.log(level, msg, *args)
16 tests/__init__.py: def _test_under_locale(testself, *args, **kwargs):
17 tests/__init__.py: return test_method(testself, *args, **kwargs)
18 tests/test_client.py: def __init__(self, *args, **kwargs):
19 tests/test_client.py: super().__init__(*args, **kwargs)
20 tests/test_config.py: def inner(command, *args, **kwargs):
21 tests/test_packetizer.py: def wrapper(*args, **kwargs):
22 tests/test_packetizer.py: result = func(*args, **kwargs)
|
| |
|
| |
|
|
|
|
|
|
|
| |
- a couple spots where we wrote longs as int64 and ints as int. I
_think_ the right thing to do here is write all ints as int64 given
how Python handles these under 3.
- docs bits
|
|
|
|
| |
Later on we can likely nuke many uses of these
|
|
|
|
|
|
|
| |
- When wrapping literals: just go away
- When wrapping variables whose values are already definitely integers (eg output of 'id()'): ditto
- When wrapping variables of unknown provenance or which are definitely
NOT integers: replaced with int()
|
|
|
|
| |
They moved from Temple Place to Franklin Street in 2005.
|
|
|
|
| |
Closes #2000
|
| |
|
|
|
|
|
| |
In some cases prefetching can lead to problems when downloading larger files. The connection to the SFTP server is disconnected due to the query behavior.
Proprietary implementations in particular tend to behave that way. Switching off prefetching is a slow but resilient solution to this problem.
|
|\ |
|
| | |
|
|\ \
| |/ |
|
| | |
|
|/
|
|
|
|
| |
Super unclear to me why both existed, even tho both
were apparently added at the same time, in the great
2013 python3-ening.
|
| |
|
|
|
|
|
|
|
| |
Choosing to skip it in some edge/corner cases where it's more harmful
than helpful. Also choosing to replace many non-%s specifiers with
regular old {} since I don't see why one would normally care. Again,
eschewing that in spots where it seems like it might matter.
|
|
|
|
|
|
|
|
| |
when running the code with python3 we get BytesWarning as what we
receive from hexlify() function is bytes. Use u() from py3compat to
overcome the issue.
Fix: https://github.com/paramiko/paramiko/issues/1074
|
|
|
|
| |
Fixes #1016, re #1012
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Thanks to bitprophet and ploxiln.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #967 #968
Rollup of earlier branches proposed as #969 and #970 with
additional fix inside sftp_client.
Includes new tests for SFTPFile usage.
Change against the 1.17 branch.
|
| | |
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
Existing just-warnings setup was old and not as rigorous as my usual.
Required a lot of stupid little changes, but now same tooling for all
projects, toot toot.
|
| | |
|
| |
| |
| |
| | |
continuations
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| |\ \
| | |/ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Original contributor probably meant to patch both of these...BUT.
Fuck copy-pasting. Fuck iiiiiit
|
| | | |
|
| | |
| | |
| | |
| | | |
Was apparently not removed when getfo() was born.
|
| |\ \ |
|
| | |\ \
| | | |/ |
|
| | | |\ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Turns out there's a reason we haven't run the strict checker
(sphinx-build -nW) before - it tries to resolve literally
every info-list field like ':raises IOError:' and sphinx
is apparently not cool enough to mesh that with intersphinx.
|
| | |/ / |
|
| |/ /
| | |
| | |
| | |
| | | |
Calling stat from inside the prefetch-body has led users to
receive IOError: The message [<filename>] is not extractable.
|
|/ /
| |
| |
| | |
Based on work of Warren Turkal
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
paramiko/transport.py
paramiko/util.py
tests/test_client.py
|
| | | |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
paramiko/channel.py
tests/test_util.py
|
| | | | |
|