On 16 Aug 2016 05:09, "Donald Stufft" wrote:
>
> Hello!
>
> I'd like to restrict what folks can upload to PyPI in an effort to help
narrow
> the scope down and to enable more a more consistent experience for
everyone.
>
> First off, we currently allow people to upload sdist,
> On Aug 15, 2016, at 7:12 PM, Glyph Lefkowitz wrote:
>
>
>> On Aug 15, 2016, at 1:56 PM, Donald Stufft wrote:
>>
>> My main thought regarding this is that bdist_dmg != all dmg files (similarly
>> for msi and wininst). These are specific files
> On Aug 15, 2016, at 1:56 PM, Donald Stufft wrote:
>
> My main thought regarding this is that bdist_dmg != all dmg files (similarly
> for msi and wininst). These are specific files created by distutils without a
> standard or without the needed work to make them truly what
On Aug 15, 2016, at 05:39 PM, Donald Stufft wrote:
>so narrowing it down to only .tar.gz and .tgz is pretty safe, but practically
>nobody uses .tgz anyways so why bother?
I agree with all of your reasoning. FWIW, I personally use .tgz all the time
when making backups of things locally, but
> On Aug 15, 2016, at 4:20 PM, Barry Warsaw wrote:
>
> On Aug 15, 2016, at 03:09 PM, Donald Stufft wrote:
>
>> Out of all of these, I think that we can easily remove bdist_dmg, bdist_rpm,
>> and bdist_dumb. I also believe that there is a strong case for removing
>> bdist_msi
On Aug 15, 2016, at 03:09 PM, Donald Stufft wrote:
>Out of all of these, I think that we can easily remove bdist_dmg, bdist_rpm,
>and bdist_dumb. I also believe that there is a strong case for removing
>bdist_msi and bdist_wininst. I also think we should consider removing
>bdist_egg.
+1 for all
> On Aug 15, 2016, at 12:09 PM, Donald Stufft wrote:
>
> Next we have bdist_dmg, bdist_msi, and bdist_winist. I'm lumping these
> together
> because they're all OS specific installers for OSs that don't already have
> some
> sort of repository. This lack of a repository
> On Aug 15, 2016, at 3:27 PM, Thomas Kluyver wrote:
>
> On Mon, Aug 15, 2016, at 08:09 PM, Donald Stufft wrote:
>> Finally, bdist_egg is quite possibly the trickiest one to justify. A fair
>> number of people still upload eggs, even though we have the wheel format.
>>
On Mon, Aug 15, 2016 at 2:30 PM, Alex Grönholm wrote:
> 15.08.2016, 22:28, Donald Stufft kirjoitti:
>>>
>>> On Aug 15, 2016, at 3:22 PM, Ian Cordasco
>>> wrote:
>>>
>>> My only thought is how we convey this message to users. I wonder if it
15.08.2016, 22:28, Donald Stufft kirjoitti:
On Aug 15, 2016, at 3:22 PM, Ian Cordasco wrote:
My only thought is how we convey this message to users. I wonder if it
would be beneficial to have Twine cut a release that warns users when
they are uploading something
> On Aug 15, 2016, at 3:22 PM, Ian Cordasco wrote:
>
> My only thought is how we convey this message to users. I wonder if it
> would be beneficial to have Twine cut a release that warns users when
> they are uploading something that will be unsupported, then have
>
On Mon, Aug 15, 2016, at 08:09 PM, Donald Stufft wrote:
> Finally, bdist_egg is quite possibly the trickiest one to justify. A fair
> number of people still upload eggs, even though we have the wheel format.
> However, I think that we should (and generally do) consider eggs to be
> deprecated and
On Mon, Aug 15, 2016 at 2:09 PM, Donald Stufft wrote:
> Hello!
>
> I'd like to restrict what folks can upload to PyPI in an effort to help narrow
> the scope down and to enable more a more consistent experience for everyone.
>
> First off, we currently allow people to upload
+1 for disallowing uploads of anything else than sdists and wheels.
15.08.2016, 22:09, Donald Stufft kirjoitti:
Hello!
I'd like to restrict what folks can upload to PyPI in an effort to help narrow
the scope down and to enable more a more consistent experience for everyone.
First off, we
Hello!
I'd like to restrict what folks can upload to PyPI in an effort to help narrow
the scope down and to enable more a more consistent experience for everyone.
First off, we currently allow people to upload sdist, bdist_wheel, bdist_egg,
bdist_dmg, bdist_dumb, bdist_msi, bdist_rpm, and
There is no email contact per se. The project tacker is here -
github.com/pypa/pip and there is a google group here -
https://groups.google.com/forum/#!forum/pypa-dev
On 13 August 2016 at 21:28, hyp3rlinx wrote:
> Can somebody here please tell me the contact email for
Can somebody here please tell me the contact email for maintainers of pip.
Thank you,
John
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
17 matches
Mail list logo