Re: [Distutils] build system requirements PEP, 3rd draft

2016-05-16 Thread Brett Cannon 
Cool, thanks!

On Mon, 16 May 2016 at 07:49 Donald Stufft  wrote:

>
> On May 16, 2016, at 10:43 AM, Brett Cannon  wrote:
>
> I'm at OSCON and in a tutorial on my work laptop so I didn't have a chance
> to verify there weren't any reST errors, so if someone with commit
> privileges can just quickly run `make` on the peps repo to make sure I
> didn't botch something that would be appreciated. :)
>
>
>
> Seems to work:
>
> $ make pep-0518.html
> pep-0518.txt (text/x-rst) -> pep-0518.html
>
> -
> Donald Stufft
> PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372
> DCFA
>
>
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] windows SSL: CERTIFICATE_VERIFY_FAILED

2016-05-16 Thread Adam GROSZER 

DOH,

To answer my own question: it's bootstrap.pypa.io not pypi... needed a 
different root cert.


On 05/16/2016 09:20 AM, Adam GROSZER wrote:

Hi,

I have here an old windows server 2003R2 (winbot.zope.org).
Recently updated python 2.7.0 to 2.7.11.
Now running into SSL: CERTIFICATE_VERIFY_FAILED with buildout bootstrap.

I installed DigiCertHighAssuranceEVRootCA.crt to "Certificates (Local
Computer)\Trusted Root Certification Authorities\Certificates.
As detailed at:
http://www.databasemart.com/howto/SQLoverssl/How_To_Install_Trusted_Root_Certification_Authority_With_MMC.aspx


But still get:


C:\buildslave\zope.testing\build>c:\Python27_32\python.exe bootstrap.py

Traceback (most recent call last):

   File "bootstrap.py", line 92, in 

 exec(urlopen('https://bootstrap.pypa.io/ez_setup.py').read(), ez)

   File "c:\Python27_32\lib\urllib2.py", line 154, in urlopen

 return opener.open(url, data, timeout)

   File "c:\Python27_32\lib\urllib2.py", line 431, in open

 response = self._open(req, data)

   File "c:\Python27_32\lib\urllib2.py", line 449, in _open

 '_open', req)

   File "c:\Python27_32\lib\urllib2.py", line 409, in _call_chain

 result = func(*args)

   File "c:\Python27_32\lib\urllib2.py", line 1240, in https_open

 context=self._context)

   File "c:\Python27_32\lib\urllib2.py", line 1197, in do_open

 raise URLError(err)

urllib2.URLError: 



--
Best regards,
 Adam GROSZER
--
Quote of the day:
It's hard to get ivory in Africa, but in Alabama the Tuscaloosa.
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] comparison of configuration languages

2016-05-16 Thread Paul Moore 
On 16 May 2016 at 16:41, Chris Barker - NOAA Federal
 wrote:
> As pointed out, it's a C lib. But as we all like writing tools, it wouldn't
> be very hard to write a Python parser for the format.

There is one (on PyPI - can't recall the name now, sorry).

> But it's a bit C-y for my taste, and yet another configure language? Really?

Also, the spec seems to imply that it doesn't support Unicode (no
Unicode escapes in strings).

Anyway, as noted this is very off-topic now, so that's all I'll say.
Paul
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] comparison of configuration languages

2016-05-16 Thread Ian Cordasco 
The PEP has been accepted by Nick. Let's turn our thoughts to more
productive topics rather than talking about a moot point.

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

Re: [Distutils] comparison of configuration languages

2016-05-16 Thread Wes Turner 
1. again, ConfigObj is pure Python, supports nesting, and is read/write (so
there is no need to template injectable config files (e.g., with  \n, =,
#;etc. must be escaped))

| PyPI: https://pypi.python.org/pypi/configobj/5.0.6
| Src: https://github.com/DiffSK/configobj
| Docs: https://configobj.readthedocs.io/en/latest/

2. A grammar for configparser would make this more apparent
https://hg.python.org/cpython/file/tip/Lib/configparser.py

On Sunday, May 15, 2016, Robert Collins  wrote:

> On 15 May 2016 at 08:21, Ionel Cristian Mărieș  > wrote:
> >
> > On Fri, May 13, 2016 at 9:22 PM, Brett Cannon  > wrote:
> >>
> >> No need to think; the decision is made and it's TOML. I know Chris
> doesn't
> >> mean to stir up trouble, but at this point if someone wants to propose
> >> something other than TOML they are going to have to write their own PEP.
> >
> >
> > Not asking for any change but has anyone looked at libconfig? It looks
> quite
> > interesting: simple grammar and nesting support. What do you think of it?
>
> I hadn't, but its certainly irrelevant here, as vendoring it suitably
> for pip would be excruciating due to the C dependency.
>
> -Rob
> ___
> 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] comparison of configuration languages

2016-05-16 Thread Chris Barker - NOAA Federal 
​Not asking for any change but has anyone looked at libconfig
? ​It looks
quite interesting: simple grammar and nesting support. What do you think of
it


As pointed out, it's a C lib. But as we all like writing tools, it wouldn't
be very hard to write a Python parser for the format.

But it's a bit C-y for my taste, and yet another configure language? Really?

-CHB



Thanks,
-- Ionel Cristian Mărieș, http://blog.ionelmc.ro
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] build system requirements PEP, 3rd draft

2016-05-16 Thread Donald Stufft 

> On May 16, 2016, at 10:43 AM, Brett Cannon  wrote:
> 
> I'm at OSCON and in a tutorial on my work laptop so I didn't have a chance to 
> verify there weren't any reST errors, so if someone with commit privileges 
> can just quickly run `make` on the peps repo to make sure I didn't botch 
> something that would be appreciated. :)


Seems to work:

$ make pep-0518.html
pep-0518.txt (text/x-rst) -> pep-0518.html

-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] build system requirements PEP, 3rd draft

2016-05-16 Thread Brett Cannon 
And the PEP is checked in! https://hg.python.org/peps/file/tip/pep-0518.txt

I'm at OSCON and in a tutorial on my work laptop so I didn't have a chance
to verify there weren't any reST errors, so if someone with commit
privileges can just quickly run `make` on the peps repo to make sure I
didn't botch something that would be appreciated. :)

On Mon, 16 May 2016 at 01:02 Paul Moore  wrote:

> On 16 May 2016 at 08:02, Nick Coghlan  wrote:
> > More seriously, as BDFL-Delegate, I'm entirely happy with this
> > version. Thanks for your work in pulling this reduced scope PEP
> > together, as well as to Robert, Nathaniel and Donald in driving the
> > preceding build system invocation PEPs.
>
> Excellent news! Thanks to all for moving this forward.
>
> Paul
>
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] build system requirements PEP, 3rd draft

2016-05-16 Thread Paul Moore 
On 16 May 2016 at 08:02, Nick Coghlan  wrote:
> More seriously, as BDFL-Delegate, I'm entirely happy with this
> version. Thanks for your work in pulling this reduced scope PEP
> together, as well as to Robert, Nathaniel and Donald in driving the
> preceding build system invocation PEPs.

Excellent news! Thanks to all for moving this forward.

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

[Distutils] windows SSL: CERTIFICATE_VERIFY_FAILED

2016-05-16 Thread Adam GROSZER 

Hi,

I have here an old windows server 2003R2 (winbot.zope.org).
Recently updated python 2.7.0 to 2.7.11.
Now running into SSL: CERTIFICATE_VERIFY_FAILED with buildout bootstrap.

I installed DigiCertHighAssuranceEVRootCA.crt to "Certificates (Local 
Computer)\Trusted Root Certification Authorities\Certificates.
As detailed at: 
http://www.databasemart.com/howto/SQLoverssl/How_To_Install_Trusted_Root_Certification_Authority_With_MMC.aspx


But still get:


C:\buildslave\zope.testing\build>c:\Python27_32\python.exe bootstrap.py

Traceback (most recent call last):

  File "bootstrap.py", line 92, in 

exec(urlopen('https://bootstrap.pypa.io/ez_setup.py').read(), ez)

  File "c:\Python27_32\lib\urllib2.py", line 154, in urlopen

return opener.open(url, data, timeout)

  File "c:\Python27_32\lib\urllib2.py", line 431, in open

response = self._open(req, data)

  File "c:\Python27_32\lib\urllib2.py", line 449, in _open

'_open', req)

  File "c:\Python27_32\lib\urllib2.py", line 409, in _call_chain

result = func(*args)

  File "c:\Python27_32\lib\urllib2.py", line 1240, in https_open

context=self._context)

  File "c:\Python27_32\lib\urllib2.py", line 1197, in do_open

raise URLError(err)

urllib2.URLError: certificate verify failed (_ssl.c:590)>


--
Best regards,
 Adam GROSZER
--
Quote of the day:
The Church has many critics but few rivals.
- Anonymous
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] build system requirements PEP, 3rd draft

2016-05-16 Thread Nick Coghlan 
On 14 May 2016 at 05:03, Brett Cannon  wrote:
> Biggest changes since the initial draft:
>
> 1. No more semantics-version
> 2. No more [package] table
> 3. Settled on [build-system] as the table name
> 4. The "requires" key is required if [build-system] is defined
> 5. Changed the title and clarified that this is all about the minimum
> requirements for the build system to execute (some added support for things
> like dynamic dependencies for producing build artifacts is for another PEP)

And lo, the colour of the bikeshed was chosen, and the chosen colour
was "teal" :)

More seriously, as BDFL-Delegate, I'm entirely happy with this
version. Thanks for your work in pulling this reduced scope PEP
together, as well as to Robert, Nathaniel and Donald in driving the
preceding build system invocation PEPs.

While it's a deviation from the nominal PEP process, I figure you can
check this into the PEPs repo in an already Accepted state, with a
reference back to this email for the Resolution. Once the PEPs repo
itself allows for pull requests, I except we'll adjust the numeric
identifier allocation process to include checking for open PRs and
using the next number not used in a current PR, rather than the next
number not used in the repo itself.

> Added a JSON Schema for the resulting data from the table because Nick likes
> his specs :)

Working for Boeing for so long left its mark :)

Cheers,
Nick.

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