Message214594
| Author | pitrou |
|---|---|
| Recipients | h.venev, pitrou |
| Date | 2014-03-23.16:05:33 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1395590733.75.0.0770519614759.issue21039@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Yes, this is by design. The occasional difference between slash-ended and non-slash-ended paths is unexpected and potentially confusing. Moreover, it's not a property of the OS itself - it's just some syntactic sugar to enable an option such as resolving symlinks. pathlib paths represent filesystem paths, not arbitrary shell arguments. Similarly, pathlib doesn't have special processing for "~someuser" parts. (as for URL paths, they are not part of the design space of pathlib) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-03-23 16:05:33 | pitrou | set | recipients: + pitrou, h.venev |
| 2014-03-23 16:05:33 | pitrou | set | messageid: <1395590733.75.0.0770519614759.issue21039@psf.upfronthosting.co.za> |
| 2014-03-23 16:05:33 | pitrou | link | issue21039 messages |
| 2014-03-23 16:05:33 | pitrou | create | |