Hi all,
Quick question about an arcane topic: currently, PEP 517 says that
paths are always represented as unicode strings. For example, when the
frontend calls build_wheel, it has to create a temporary dir to hold
the output wheel, and it passes this in as an absolute path
represented as a unicod
This was discussed several years ago in
https://mail.python.org/pipermail/distutils-sig/2015-May/026381.html and a few
other threads. The final phases went out earlier this year. I don't think there
is any plan to re-enable uploads to pythonhosted at this time. If you want a
one-off redirect ch
I think it's wise to revert that commit. It seems pythonhosted only
suggested to migrate to RTD but there never was an official shutdown date
or warning (either via direct email or message on the web page).
On Tue, Sep 5, 2017 at 12:19 PM, Berker Peksağ
wrote:
> On Mon, Sep 4, 2017 at 4:56 PM, N
On Mon, Sep 4, 2017 at 4:56 PM, Nick Coghlan wrote:
> On 2 September 2017 at 15:34, Giampaolo Rodola' wrote:
>> I know it was deprecated long ago in favor of readthedocs but I kept
>> postponing it and my doc is still hosted on
>> https://pythonhosted.org/psutil/.
>
> While we've talked about dep
Thanks a lot Nick. I filed a bug:
https://github.com/pypa/pypi-legacy/issues/700
On Mon, Sep 4, 2017 at 9:56 PM, Nick Coghlan wrote:
> On 2 September 2017 at 15:34, Giampaolo Rodola'
> wrote:
> > I know it was deprecated long ago in favor of readthedocs but I kept
> > postponing it and my doc i
Supposedly there is some meeting tomorrow concerning the wheel project that
will determine the fate of dist_info. So that is why I bought it up.
On Sep 4, 2017 9:00 PM, "Chris Jerdonek" wrote:
> On Mon, Sep 4, 2017 at 6:41 PM, xoviat wrote:
> > The PR that I am taking about is not for pip but f
On Mon, Sep 4, 2017 at 6:41 PM, xoviat wrote:
> The PR that I am taking about is not for pip but for the wheel project.
Okay, well you started the thread asking something similar for your
pip PR (see below). I'm sure similar considerations hold for the wheel
project.
On Mon, Sep 4, 2017 at 5:11
The PR that I am taking about is not for pip but for the wheel project.
On Sep 4, 2017 8:19 PM, "Chris Jerdonek" wrote:
> On Mon, Sep 4, 2017 at 6:08 PM, xoviat wrote:
> > In any case, we're going to need this for prepare_metadata, so the
> question
> > you should ask is: what are the reasons f
On Mon, Sep 4, 2017 at 6:08 PM, xoviat wrote:
> In any case, we're going to need this for prepare_metadata, so the question
> you should ask is: what are the reasons for *not* merging this? I haven't
> heard any so far but that doesn't mean that they don't exist. If there are
> none, then I don't
On Mon, Sep 4, 2017 at 5:51 PM, xoviat wrote:
>> The only reason I can think of that setuptools would need a dist_info
> command would be to implement the PEP 517 prepare_wheel_metadata hook.
>
> Yes. That is absolutely correct.
>
>> But this hook is optional and in fact provides no value right no
In any case, we're going to need this for prepare_metadata, so the question
you should ask is: what are the reasons for *not* merging this? I haven't
heard any so far but that doesn't mean that they don't exist. If there are
none, then I don't see why we cannot merge my wheel PR and do a release.
> The only reason I can think of that setuptools would need a dist_info
command would be to implement the PEP 517 prepare_wheel_metadata hook.
Yes. That is absolutely correct.
> But this hook is optional and in fact provides no value right now, so
it can't be a blocker for anything.
The simplest
On Mon, Sep 4, 2017 at 5:09 PM, xoviat wrote:
> Nathaniel:
>
> Pip requires egg_info to discover dependencies of source distributions so
> that it can build wheels all at once after downloading the requirements. I
> need to move pip off of egg_info as soon as possible and dist_info is
> required t
Also if someone with pip write access could please discuss and hopefully
merge my initial PR on pip, I would very much appreciate it. Paul seems to
be short on time.
2017-09-04 19:09 GMT-05:00 xoviat :
> Nathaniel:
>
> Pip requires egg_info to discover dependencies of source distributions so
> th
Nathaniel:
Pip requires egg_info to discover dependencies of source distributions so
that it can build wheels all at once after downloading the requirements. I
need to move pip off of egg_info as soon as possible and dist_info is
required to do that.
2017-09-03 21:00 GMT-05:00 Nathaniel Smith :
Wheel has always implemented dist info by converting from egg info. It is
necessary to invoke all of the egg info writers provided by setuptools or
tons of packages will break. But so far dist info has only been generated
as part of building a wheel.
On Sun, Sep 3, 2017, 22:01 Nathaniel Smith wro
Yeah, so we should maybe start using the upcoming v1.3 metadata when the
related PEP is accepted...?
Daniel Holth kirjoitti 04.09.2017 klo 17:48:
Well, none of the metadata generated by bdist wheel conforms to an
accepted pep. But if you rely on the json file then you won't be
interoperable
Well, none of the metadata generated by bdist wheel conforms to an accepted
pep. But if you rely on the json file then you won't be interoperable with
wheels from any other generator.
On Mon, Sep 4, 2017, 10:06 Alex Grönholm wrote:
> Yes, I see the inclusion of a metadata file which conforms to
Yes, I see the inclusion of a metadata file which conforms to an
unaccepted PEP as potentially dangerous.
Perhaps I should disable it in the next release?
Daniel Holth kirjoitti 04.09.2017 klo 17:03:
Some people enjoy using metadata.json which tracked pep 426 but I have
been meaning to take
Some people enjoy using metadata.json which tracked pep 426 but I have been
meaning to take it out, and perhaps keep the key/value to json converter as
a command.
On Mon, Sep 4, 2017, 09:33 Nick Coghlan wrote:
> Some time ago, I started the process [1] of adjusting how
> distutils-sig uses the P
On 2 September 2017 at 15:34, Giampaolo Rodola' wrote:
> I know it was deprecated long ago in favor of readthedocs but I kept
> postponing it and my doc is still hosted on
> https://pythonhosted.org/psutil/.
While we've talked about deprecating it, it *hasn't* been deprecated.
Looking at https://
Some time ago, I started the process [1] of adjusting how
distutils-sig uses the PEP process so that the reference
specifications will live on packaging.python.org, and we use the PEP
process to manage *changes* to those specifications, rather than
serving as the specifications themselves (that is,
On 3 September 2017 at 05:42, Donald Stufft wrote:
> On Sep 1, 2017, at 2:30 PM, Chris Barker wrote:
>> Do the Linux distros use pip to build their packages?
>
> Not that I am aware of.
Fedora's build macros for Python projects currently rely on running
setup.py directly, but we've been consider
23 matches
Mail list logo