[issue9261] include higher (../../) dirs fails

Changes by Éric Araujo : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue9261] include higher (../../) dirs fails

Éric Araujo added the comment: I think disallowing .. is fine, so I’m assigning to myself to make sure I’ll take time later to check the docs. -- assignee: tarek -> merwok ___ Python tracker __

[issue9261] include higher (../../) dirs fails

Éric Araujo added the comment: Can you tell if the docs fail to mention that? If they do, please reopen this as a documentation bug (change title, select component Documentation, and set status to open). Thank you! -- nosy: +merwok ___ Python track

[issue9261] include higher (../../) dirs fails

Dan OD added the comment: Sorry for all the noise - this dynamic link thing seems to be fixed in 2.7 rendering this report 'closed' Dan -- status: open -> closed ___ Python tracker ___

[issue9261] include higher (../../) dirs fails

Dan OD added the comment: Thinking about this - maybe including dirs above ./ is bad as it's not obvious where they should live in the sdist. My alternative would be to create links to ../../this in ./ but then distutils creates links rather than hard copies in sdist - is this something that

[issue9261] include higher (../../) dirs fails

New submission from Dan OD : MANIFEST.in example: recursive-include ../../this *.that fails to include files with "warning: no files found matching '*.that' under directory '../../this'" and also include ../../this *.that fails with "warning: no files found matching '../../this'" - odd si