On 04/27/2016 02:45 PM, Paul Moore wrote:
On 27 April 2016 at 18:39, Ethan Furman wrote:
# Upload the files once you've checked them
twine upload *.whl dist/* # because setup.py upload can't upload prebuilt files
What a pain. :(
Personally, I agree with Donald that the "normal" process o
On 27 April 2016 at 18:39, Ethan Furman wrote:
> My current process is:
>
> python3.5 setup.py sdist --format=gztar,zip bdist_wheel upload
>
> What should I be doing instead?
My suggestion would be
# Build the sdist
python3.5 setup.py sdist --format=gztar,zip
# Build the wheel *from that sdist
On 04/27/2016 12:18 PM, Daniel Holth wrote:
To answer the original question, report the bug here
https://bitbucket.org/pypa/wheel
What do you know, it's already there! ;)
https://bitbucket.org/pypa/wheel/issues/99/cannot-exclude-directory
--
~Ethan~
On Wed, Apr 27, 2016 at 2:18 PM, Daniel Holth wrote:
> To answer the original question, report the bug here
> https://bitbucket.org/pypa/wheel
>
It looksl ike there's already a similar bug opened at
https://bitbucket.org/pypa/wheel/issues/147/bdist_wheel-should-start-by-cleaning-up
I ran into t
To answer the original question, report the bug here
https://bitbucket.org/pypa/wheel
On Wed, Apr 27, 2016 at 3:10 PM Ethan Furman wrote:
> On 04/27/2016 12:00 PM, Alex Grönholm wrote:
>
> > The sdist should include all the source files, including tests and
> > documentation. In binary distribut
On 04/27/2016 12:00 PM, Alex Grönholm wrote:
The sdist should include all the source files, including tests and
documentation. In binary distributions, however, they are just dead
weight. Do you want the full documentation and test suites to be
installed for every single dependency when you depl
The sdist should include all the source files, including tests and
documentation. In binary distributions, however, they are just dead
weight. Do you want the full documentation and test suites to be
installed for every single dependency when you deploy your application?
I sure don't.
27.04.2
On 04/27/2016 11:13 AM, Alex Grönholm wrote:
Are you seriously saying that you want your bdists to include tests,
documentation etc.?
However you and I agree or disagree on what should be in a bdist, the
command I ran should have produced a bdist based on the sdists I just
created in the sam
Whatever the ideal situation (not using distutils at all would be a
suggestion) bdist_wheel certainly has some simple bugs that make it less
fun to use sometimes.
On Wed, Apr 27, 2016 at 2:14 PM Alex Grönholm
wrote:
> Are you seriously saying that you want your bdists to include tests,
> documen
On Apr 27 2016, at 2:09 pm, Ethan Furman wrote:
> On 04/27/2016 10:52 AM, Donald Stufft wrote:
>
> > This isn't really a problem with what you're doing. Rather it's an
issue
> with the toolchain and and open question whether or not wheels should
> conceptually be able
Are you seriously saying that you want your bdists to include tests,
documentation etc.?
Most developers would not agree with you, including yours truly.
27.04.2016, 21:10, Ethan Furman kirjoitti:
On 04/27/2016 10:52 AM, Donald Stufft wrote:
This isn't really a problem with what you're doing.
No I mean the build directory.
On Wed, Apr 27, 2016, 14:11 Ethan Furman wrote:
> On 04/27/2016 11:05 AM, Daniel Holth wrote:
>
> > Bdist_wheel just doesn't understand MANIFEST.in . Perhaps support could
> > be adapted from bdist_egg or other bdist implementations. Wheel doesn't
> > do everything
On 04/27/2016 11:05 AM, Daniel Holth wrote:
Bdist_wheel just doesn't understand MANIFEST.in . Perhaps support could
be adapted from bdist_egg or other bdist implementations. Wheel doesn't
do everything the setuptools or distutils implementations put into their
dist commands. Even something as si
You can try to patch around the problem (and do it in every single alternative
build system once we enable support for that) or you can just fix the problem
at the "protocol" level once and for all. The fundamental problem isn't with
MANIFEST.in, it's that some indeterminite steps need to run to pr
On 04/27/2016 10:52 AM, Donald Stufft wrote:
This isn't really a problem with what you're doing. Rather it's an issue
with the toolchain and and open question whether or not wheels should
conceptually be able to be produced from a checkout, or if they should
only be produced from a sdist. Proble
I feel differently.
Bdist_wheel just doesn't understand MANIFEST.in . Perhaps support could be
adapted from bdist_egg or other bdist implementations. Wheel doesn't do
everything the setuptools or distutils implementations put into their dist
commands. Even something as simple as a forced clean of
This isn't really a problem with what you're doing. Rather it's an issue with
the toolchain and and open question whether or not wheels should conceptually
be able to be produced from a checkout, or if they should only be produced
from a sdist. Problems like this are why I advocate the Checkout ->
On 04/26/2016 07:10 AM, Donald Stufft wrote:
Alternatively, he could have just produced a wheel from any checkout at
all if the MANIFEST.in excluded a file that would otherwise have been
installed.
Yes. My MANIFEST.in starts with an 'exclude enum/*' and then includes
all files it wants.
T
18 matches
Mail list logo