Don't use os.path.join for remote paths

[bitprophet]

Description

In most places (SFTP-ly speaking) we assume the remote end uses Unix style forward slashes because there is no reliable way to detect the remote OS, and (AFAIK) even Windows-based remote SSH/SFTP clients use forward slashes anyway.

Thus, our os.path.join policy should be to use os.path.join for local paths but not for remote paths, which should always use /.

Unfortunately, we do not do this consistently, leading Windows client users to run into problems when using put and get. fabric/sftp.py is littered with os.path.join.

So, we should:

• Develop (or copy, ideally) our own version of os.path.join hardcoded to use a Unix-style separator
• Use that instead of os.path.join for all remote contexts

---

Originally submitted by Jeff Forcier (bitprophet) on 2011-03-07 at 06:30pm EST

Attachments

• posixpath.patch

Relations

• Duplicated by put command incorrectly assembles remote_path on Windows #356: put command incorrectly assembles remote_path on Windows
• Duplicated by Put is using the local machines Path functions instead of the remote machine's. #405: Put is using the local machines Path functions instead of the remote machine's.

[bitprophet]

Eric Hanchrow (offby1) posted:

---

done as far as can reasonably be tested, here.

---

on 2011-03-14 at 12:44am EDT

[bitprophet]

**** (adamjernst) posted:

---

Well it seems this is done, but you could also import the "posixpath" module which should be available on all platforms, and uses / as the separator. This has the advantage of hewing to a well-defined spec (POSIX).

---

on 2011-03-14 at 10:14pm EDT

[bitprophet]

Jeff Forcier (bitprophet) posted:

---

Chris -- can you point me to the specific commits or branch for your changes? Having a hard time parsing the general commit list for that GH link.

Adam -- is posixpath available by default on Windows? The docs are unclear and I've no Windows box to test on right now.

---

on 2011-04-22 at 05:11pm EDT

[bitprophet]

Jason R. Coombs (jaraco) posted:

---

confirmed: posixpath is available on all platforms by default.

---

on 2011-05-25 at 02:20pm EDT

[bitprophet]

Jason R. Coombs (jaraco) posted:

---

I've added another commit (https://github.com/jaraco/fabric/commit/0a592f185783a1331816733565bb0ac005e9f714) to my fork which incorporates the additional locations where remote paths were using os.path.join.

---

on 2011-05-25 at 02:30pm EDT

[bitprophet]

Christian Long (christianmlong) posted:

---

I applied Jason's posixpath fixes to Fabric 1.0.1. See attached patch file. Works on Windows XP, Python 2.5.

---

on 2011-06-01 at 12:08pm EDT

[bitprophet]

Jeff Forcier (bitprophet) posted:

---

Christian Long wrote:

I applied Jason's posixpath fixes to Fabric 1.0.1. See attached patch file. Works on Windows XP, Python 2.5.

Awesome, thanks. This was actually next on my list for tackling (trying to get 1.0.2 and 1.1 out soon) so you have good timing.

---

on 2011-06-01 at 05:09pm EDT

[bitprophet]

Yannick Jost (yanjost) posted:

---

Still not in 1.2 ?

---

on 2011-07-22 at 07:39am EDT

[yuntaoL]

I have same issue, but seems it is not addressed in 1.2

[bitprophet]

Protip: ticket status is a great indicator of whether something has been released or not ;) Also, changelogs.

This ticket is open, and is not listed in the 1.2 changelog, so no, it has not been fixed yet. The best way to keep track is to just watch this ticket -- I will comment (or you will see commit message notes & its status going to 'Closed') when it's fixed :)

[bitprophet]

Fixed via #570.