Re: [Distutils] Source of confusion

[Nick Coghlan]

On 30 March 2017 at 01:27, Jelle Zijlstra  wrote:
>
>
> 2017-03-29 2:31 GMT-07:00 Thomas Güttler :
>>
>>
>>
>> Am 29.03.2017 um 09:51 schrieb Paul Moore:
>>>
>>> On 29 March 2017 at 06:29, Thomas Güttler 
>>> wrote:

 I am stupid and missing a guiding hand which gives me simple straight
 forward step by step instruction.
>>>
>>>
>>> To do what?
>>
>>
>> To find canonical docs. With "canonical" I mean current docs from the
>> upstream.
>>
> Are you aware of https://packaging.python.org/ ?

As an opinionated-but-still-free combination of tools, there's also
Kenneth Reitz's pipenv: https://github.com/kennethreitz/pipenv

Understandably, that's mainly geared towards network service hosting
environments like Heroku, but it also works pretty well for command
line apps, testing environment setups, etc.

However, none of the available options will get away from the fact
that only end users know their own operational requirements - we can't
provide a single universal right answer, because there isn't a single
universal use case.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] obtaining project name and packages

[Wes Turner]

cd ./lib/python2.7/site-packages/notebook-4.4.1.dist-info
cat metadata.json | python -m json.tool

{
"classifiers": [
"Intended Audience :: Developers",
"Intended Audience :: System Administrators",
"Intended Audience :: Science/Research",
"License :: OSI Approved :: BSD License",
"Programming Language :: Python",
"Programming Language :: Python :: 2.7",
"Programming Language :: Python :: 3"
],
"extensions": {
"python.commands": {
"wrap_console": {
"jupyter-nbextension": "notebook.nbextensions:main",
"jupyter-notebook": "notebook.notebookapp:main",
"jupyter-serverextension": "notebook.serverextensions:main"
}
},
"python.details": {
"contacts": [
{
"email": "jupy...@googlegroups.com",
"name": "Jupyter Development Team",
"role": "author"
}
],
"document_names": {
"description": "DESCRIPTION.rst"
},
"project_urls": {
"Home": "http://jupyter.org;
}
},
"python.exports": {
"console_scripts": {
"jupyter-nbextension": "notebook.nbextensions:main",
"jupyter-notebook": "notebook.notebookapp:main",
"jupyter-serverextension": "notebook.serverextensions:main"
}
}
},
"extras": [
"doc",
"test"
],
"generator": "bdist_wheel (0.29.0)",
"keywords": [
"Interactive",
"Interpreter",
"Shell",
"Web"
],
"license": "BSD",
"metadata_version": "2.0",
"name": "notebook",
"platform": "Linux",
"run_requires": [
{
"extra": "doc",
"requires": [
"Sphinx (>=1.1)"
]
},
{
"requires": [
"ipykernel",
"ipython-genutils",
"jinja2",
"jupyter-client",
"jupyter-core",
"nbconvert",
"nbformat",
"tornado (>=4)",
"traitlets"
]
},
{
"extra": "test",
"requires": [
"nose",
"requests"
]
},
{
"environment": "python_version == \"2.7\"",
"extra": "test",
"requires": [
"mock"
]
},
{
"environment": "sys_platform != \"win32\"",
"requires": [
"terminado (>=0.3.3)"
]
}
],
"summary": "A web-based notebook environment for interactive computing",
"version": "4.4.1"
}


On Wed, Mar 29, 2017 at 3:19 PM, Wes Turner  wrote:

>
>
> On Wed, Mar 29, 2017 at 1:55 PM, Thomas Kluyver 
> wrote:
>
>> I have a tool that does this from a wheel:
>> https://github.com/takluyver/wheeldex
>>
>> From an sdist, I think you need to either build a wheel or install it
>> before you can get this information reliably.
>>
>
> Src: https://code.launchpad.net/~tseaver/pkginfo/trunk
>
> PyPI: https://pypi.python.org/pypi/pkginfo
>
> This package provides an API for querying the distutils metadata written
>> in the PKG-INFO file inside a source distriubtion (an sdist) or a binary
>> distribution (e.g., created by running bdist_egg). It can also query the
>> EGG-INFO directory of an installed distribution, and the *.egg-info stored
>> in a “development checkout” (e.g, created by running setup.py develop).
>>
>
> Docs: https://pythonhosted.org/pkginfo/
>
> https://bazaar.launchpad.net/~tseaver/pkginfo/trunk/files/
> head:/pkginfo/tests/
>
>
>> Some of my installed packages have a 'top_level.txt' file in the
>> .dist-info folder, containing a list of the top-level package names
>> installed by that distribution. I don't believe this is formally
>> specified anywhere, though, and packages created by flit do not have it.
>>
>> Thomas
>>
>> On Wed, Mar 29, 2017, at 07:41 PM, Chris Jerdonek wrote:
>> > Hi, this seems like a simple question, but I haven't been able to find
>> > the answer online:
>> >
>> > What is the current recommended way to get (1) the name of a project,
>> > and (2) the names of the top-level packages installed by a project
>> > (not counting the project's dependencies).  You have access to / can
>> > run the project's setup.py, and you're also allowed to assume that the
>> > project is installed.
>> >
>> > For example, for (1) I know you can do--
>> >
>> > $ python setup.py --name
>> >
>> > But I'm not sure if accessing setup.py is no longer recommended (as
>> > opposed to going through a tool like pip).
>> >
>> > Thanks a lot,
>> > --Chris
>> > ___
>> > Distutils-SIG 

Re: [Distutils] obtaining project name and packages

[Wes Turner]

On Wed, Mar 29, 2017 at 1:55 PM, Thomas Kluyver 
wrote:

> I have a tool that does this from a wheel:
> https://github.com/takluyver/wheeldex
>
> From an sdist, I think you need to either build a wheel or install it
> before you can get this information reliably.
>

Src: https://code.launchpad.net/~tseaver/pkginfo/trunk

PyPI: https://pypi.python.org/pypi/pkginfo

This package provides an API for querying the distutils metadata written in
> the PKG-INFO file inside a source distriubtion (an sdist) or a binary
> distribution (e.g., created by running bdist_egg). It can also query the
> EGG-INFO directory of an installed distribution, and the *.egg-info stored
> in a “development checkout” (e.g, created by running setup.py develop).
>

Docs: https://pythonhosted.org/pkginfo/

https://bazaar.launchpad.net/~tseaver/pkginfo/trunk/files/head:/pkginfo/tests/


> Some of my installed packages have a 'top_level.txt' file in the
> .dist-info folder, containing a list of the top-level package names
> installed by that distribution. I don't believe this is formally
> specified anywhere, though, and packages created by flit do not have it.
>
> Thomas
>
> On Wed, Mar 29, 2017, at 07:41 PM, Chris Jerdonek wrote:
> > Hi, this seems like a simple question, but I haven't been able to find
> > the answer online:
> >
> > What is the current recommended way to get (1) the name of a project,
> > and (2) the names of the top-level packages installed by a project
> > (not counting the project's dependencies).  You have access to / can
> > run the project's setup.py, and you're also allowed to assume that the
> > project is installed.
> >
> > For example, for (1) I know you can do--
> >
> > $ python setup.py --name
> >
> > But I'm not sure if accessing setup.py is no longer recommended (as
> > opposed to going through a tool like pip).
> >
> > Thanks a lot,
> > --Chris
> > ___
> > Distutils-SIG maillist  -  Distutils-SIG@python.org
> > https://mail.python.org/mailman/listinfo/distutils-sig
> ___
> Distutils-SIG maillist  -  Distutils-SIG@python.org
> https://mail.python.org/mailman/listinfo/distutils-sig
>
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] obtaining project name and packages

[Thomas Kluyver]

I have a tool that does this from a wheel:
https://github.com/takluyver/wheeldex

>From an sdist, I think you need to either build a wheel or install it
before you can get this information reliably.

Some of my installed packages have a 'top_level.txt' file in the
.dist-info folder, containing a list of the top-level package names
installed by that distribution. I don't believe this is formally
specified anywhere, though, and packages created by flit do not have it.

Thomas

On Wed, Mar 29, 2017, at 07:41 PM, Chris Jerdonek wrote:
> Hi, this seems like a simple question, but I haven't been able to find
> the answer online:
> 
> What is the current recommended way to get (1) the name of a project,
> and (2) the names of the top-level packages installed by a project
> (not counting the project's dependencies).  You have access to / can
> run the project's setup.py, and you're also allowed to assume that the
> project is installed.
> 
> For example, for (1) I know you can do--
> 
> $ python setup.py --name
> 
> But I'm not sure if accessing setup.py is no longer recommended (as
> opposed to going through a tool like pip).
> 
> Thanks a lot,
> --Chris
> ___
> Distutils-SIG maillist  -  Distutils-SIG@python.org
> https://mail.python.org/mailman/listinfo/distutils-sig
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

[Distutils] obtaining project name and packages

[Chris Jerdonek]

Hi, this seems like a simple question, but I haven't been able to find
the answer online:

What is the current recommended way to get (1) the name of a project,
and (2) the names of the top-level packages installed by a project
(not counting the project's dependencies).  You have access to / can
run the project's setup.py, and you're also allowed to assume that the
project is installed.

For example, for (1) I know you can do--

$ python setup.py --name

But I'm not sure if accessing setup.py is no longer recommended (as
opposed to going through a tool like pip).

Thanks a lot,
--Chris
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] Source of confusion

[Jelle Zijlstra]

2017-03-29 2:31 GMT-07:00 Thomas Güttler :

>
>
> Am 29.03.2017 um 09:51 schrieb Paul Moore:
>
>> On 29 March 2017 at 06:29, Thomas Güttler 
>> wrote:
>>
>>> I am stupid and missing a guiding hand which gives me simple straight
>>> forward step by step instruction.
>>>
>>
>> To do what?
>>
>
> To find canonical docs. With "canonical" I mean current docs from the
> upstream.
>
> Are you aware of https://packaging.python.org/ ?

> Regards,
>   Thomas
>
>
>
>
>
> --
> Thomas Guettler http://www.thomas-guettler.de/
>
> ___
> Distutils-SIG maillist  -  Distutils-SIG@python.org
> https://mail.python.org/mailman/listinfo/distutils-sig
>
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] Source of confusion

[Paul Moore]

On 29 March 2017 at 10:31, Thomas Güttler  wrote:
> Am 29.03.2017 um 09:51 schrieb Paul Moore:
>>
>> On 29 March 2017 at 06:29, Thomas Güttler 
>> wrote:
>>>
>>> I am stupid and missing a guiding hand which gives me simple straight
>>> forward step by step instruction.
>>
>>
>> To do what?
>
> To find canonical docs. With "canonical" I mean current docs from the
> upstream.

I think Nick's point probably covers this discussion, but you haven't
said what you want docs *for*. pip? setuptools? wheel? something else?
They are in various places, which you can hunt out via pypi or google.
It's not hard to do, but certainly it's true that it's harder to find
things than you'd want if you were paying for a well-documented
service. But given that you're not paying anything, and no-one working
on Python packaging has any obligation to meet your expectations,
you'll need to either lower the level of your expectations, pay
someone to provide what you're looking for, or offer your own time and
energy to address the issues you find. Simply making vague complaints
on this list isn't particularly productive.

Sorry if that's not the response you were hoping for, and in
particular if you have a pressing need for support that we're not
providing, I do understand how that can be a problem for you, but as
Nick says, this is the reality of relying on software that's provided
to you free of charge.

Paul
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] Source of confusion

[Thomas Güttler]

Am 29.03.2017 um 09:51 schrieb Paul Moore:

On 29 March 2017 at 06:29, Thomas Güttler  wrote:

I am stupid and missing a guiding hand which gives me simple straight forward 
step by step instruction.


To do what?


To find canonical docs. With "canonical" I mean current docs from the upstream.

Regards,
  Thomas





--
Thomas Guettler http://www.thomas-guettler.de/
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] Source of confusion

[Nick Coghlan]

On 29 March 2017 at 17:51, Paul Moore  wrote:
> On 29 March 2017 at 06:29, Thomas Güttler  
> wrote:
>> I am stupid and missing a guiding hand which gives me simple straight 
>> forward step by step instruction.
>
> To do what?

As far as I can tell, to get a customer experience instead of a
prospective co-contributor one.

I'm sorry Thomas, as long as you continue looking for a coherent
customer experience from a collaborative collection of volunteer-run
community projects, you're going to continually be confused and
disappointed.

The Python ecosystem *does* include commercial vendors that offer to
make opinionated technical decisions on behalf of their customers, as
well as providing a single point of contact for support questions and
feature requests, but beyond that, offering an overwhelming array of
confusing choices is pretty much the way open source *works*.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] Source of confusion

[Paul Moore]

On 29 March 2017 at 06:29, Thomas Güttler  wrote:
> I am stupid and missing a guiding hand which gives me simple straight forward 
> step by step instruction.

To do what?
Paul
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig