cpython/.azure-pipelines
Greg Price 9ece4a5057 Unmark files as executable that can't actually be executed. (GH-15353)
There are plenty of legitimate scripts in the tree that begin with a
`#!`, but also a few that seem to be marked executable by mistake.

Found them with this command -- it gets executable files known to Git,
filters to the ones that don't start with a `#!`, and then unmarks
them as executable:

    $ git ls-files --stage \
      | perl -lane 'print $F[3] if (!/^100644/)' \
      | while read f; do
          head -c2 "$f" | grep -qxF '#!' \
          || chmod a-x "$f"; \
        done

Looking at the list by hand confirms that we didn't sweep up any
files that should have the executable bit after all.  In particular

 * The `.psd` files are images from Photoshop.

 * The `.bat` files sure look like things that can be run.
   But we have lots of other `.bat` files, and they don't have
   this bit set, so it must not be needed for them.



Automerge-Triggered-By: @benjaminp
2019-08-20 21:53:59 -07:00
..
windows-release bpo-37354: Sign Activate.ps1 for release (GH-15235) 2019-08-12 14:09:36 -07:00
ci.yml bpo-37081: Test with OpenSSL 1.1.1c (GH-13631) 2019-06-03 20:10:19 +02:00
docs-steps.yml Doc: Bump Sphinx verison. (#13785) 2019-06-15 15:41:58 +02:00
macos-steps.yml
posix-deps-apt.sh Unmark files as executable that can't actually be executed. (GH-15353) 2019-08-20 21:53:59 -07:00
posix-steps.yml Temporary workaround for an ACL issue on Ubuntu on Azure Pipelines (GH-12649) 2019-04-01 09:10:20 -07:00
pr.yml bpo-37081: Test with OpenSSL 1.1.1c (GH-13631) 2019-06-03 20:10:19 +02:00
prebuild-checks.yml
windows-layout-steps.yml bpo-35683: Improve Azure Pipelines steps (GH-11493) 2019-01-22 10:49:52 -08:00
windows-release.yml Enable publish of Windows releases through Azure Pipelines (GH-14720) 2019-07-13 11:46:16 +02:00
windows-steps.yml bpo-35683: Improve Azure Pipelines steps (GH-11493) 2019-01-22 10:49:52 -08:00