[issue26445] setup.py sdist mishandles package_dir option

[glep]

New submission from glep:

Suppose I have a setup.py with the option

   ...
   packages=['package', 'package.utils'],
   package_dir={'package.utils', '../utils'},
   ...

as would arise if ../utils was a package shared between several projets 
('package', 'package1', ...).

I would expect the source distribution created by 'python setup.py sdist'
to create an archive with the following structure:

   /
   |-- package/
   |-- package/utils

And this is indeed what *bdist* does. BUT *sdist* copies '../utils' in 
'package/../utils' instead of 'package/utils', with the result that utils is 
outside of the distribution altogether. 

The issue is referenced in a couple of StackOverflow posts that have attracted 
little attention so far, for example:

http://stackoverflow.com/questions/35510972/inconsistent-behaviour-of-bdist-vs-sdist-when-distributing-a-python-package

--
components: Distutils
messages: 260904
nosy: dstufft, eric.araujo, glep
priority: normal
severity: normal
status: open
title: setup.py sdist mishandles package_dir option
type: behavior
versions: Python 2.7

___
Python tracker 
<http://bugs.python.org/issue26445>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26445] setup.py sdist mishandles package_dir option

[glep]

glep added the comment:

Actually I have come to realise that this is the intended behaviour for source 
distributions. And that it is simply not possible to pull in a package from 
outside the current top-level package when building a source distribution.

--
resolution:  -> not a bug
status: open -> closed

___
Python tracker 
<http://bugs.python.org/issue26445>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com