Bug Report

Describe the bug
With

namespace_packages=[‘paste’]

in setup() command in setup.py, tests fail, because the installation is done incorrectly. When this line is removed all tests pass.

To Reproduce
Steps to reproduce the behavior:

1. build package, install it, run tests with pytest -v command.

Actual behavior
All tests error with traceback like:

[   35s] ___________________ ERROR collecting tests/test_basic_app.py ___________________
[   35s] ImportError while importing test module '/home/abuild/rpmbuild/BUILD/pastedeploy-2.1.0/tests/test_basic_app.py'.
[   35s] Hint: make sure your test modules/packages have valid Python names.
[   35s] Traceback:
[   35s] tests/test_basic_app.py:1: in <module>
[   35s]     from paste.deploy import loadapp
[   35s] E   ModuleNotFoundError: No module named 'paste.deploy'

Expected behavior
Tests pass

Additional context
complete build log

Get Support

To get help or technical support, see Get Support.

Bug Report

Please search the issue tracker for similar issues before submitting a new issue.

Describe the bug

A clear and concise description of the bug.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://pypi.org/project/PasteDeploy/#files
2. Download PasteDeploy-2.1.1-py2.py3-none-any.whl
3. Install it
4. dist-info folder is missing license file

Expected behavior
License included in wheel package

Additional context
The license file is included in source release, but not in wheel on PyPI

See discussions:
astropy/astropy#11091
pypa/pip#7413
pypa/setuptools#3279

[tkloczko@devel-g2v pastedeploy-2.1.1]$ grep -r pkg_resources
docs/conf.py:import pkg_resources
docs/conf.py:version = pkg_resources.get_distribution('pastedeploy').version
paste/__init__.py:    import pkg_resources
paste/__init__.py:    pkg_resources.declare_namespace(__name__)
paste/__init__.py:    # don't prevent use of paste if pkg_resources isn't installed
paste/deploy/config.py:            import pkg_resources
paste/deploy/config.py:            pkg_resources.require('Paste')
paste/deploy/loadwsgi.py:import pkg_resources
paste/deploy/loadwsgi.py:    ep = pkg_resources.EntryPoint.parse("x=" + s)
paste/deploy/loadwsgi.py:                pkg_resources.require(spec)
paste/deploy/loadwsgi.py:            distribution=pkg_resources.get_distribution(self.spec),
paste/deploy/loadwsgi.py:                pkg_resources.require(self.spec)
paste/deploy/loadwsgi.py:                entry = pkg_resources.get_entry_info(
paste/deploy/loadwsgi.py:            dist = pkg_resources.get_distribution(self.spec)
paste/deploy/loadwsgi.py:                dictkeys(pkg_resources.get_entry_info(self.spec, prot, name) or {})
tests/__init__.py:import pkg_resources
tests/__init__.py:pkg_resources.require('PasteDeploy')
tests/fixture.py:from pkg_resources import *
tests/test_load_package.py:import pkg_resources
tests/test_load_package.py:    print_(pkg_resources.require('FakeApp'))

Issue

Installing pyramid==1.9.1 on a Python 2.7 environment also installs PasteDeploy-3.0 which doesn't seem to be compatible with Python 2.7.

Error

Traceback (most recent call last):
  File "/Users/user/.virtualenvs/myproject/bin/pserve", line 8, in <module>
    sys.exit(main())
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/pyramid/scripts/pserve.py", line 32, in main
    return command.run()
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/pyramid/scripts/pserve.py", line 167, in run
    loader = self._get_config_loader(config_uri)
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/pyramid/scripts/common.py", line 23, in get_config_loader
    return plaster.get_loader(config_uri, protocols=['wsgi'])
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/plaster/loaders.py", line 116, in get_loader
    loader = loader_info.load(config_uri)
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/plaster/loaders.py", line 204, in load
    return self.factory(config_uri)
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/plaster/loaders.py", line 199, in factory
    self._factory = self.entry_point.load()
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2443, in load
    return self.resolve()
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2449, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/plaster_pastedeploy/__init__.py", line 7, in <module>
    from paste.deploy import loadapp, loadserver, loadfilter, appconfig
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/paste/deploy/__init__.py", line 3, in <module>
    from paste.deploy.loadwsgi import *  # noqa F401,F403
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 82
    args[0] = f'Error in file {parser.filename}: {e}'

Observation

The setup.cfg definition is missing the python_requires instruction.

See: #2 (comment)

https://bitbucket.org/cdent/pastescript

Upon migration, the links to the Paste Script docs need to be updated.

The README is out of date with regard to the new hosting in the pylons organization and should be updated to reflect the current state of affairs.

In Python 2 I got into the habit of using the same .ini file for uwsgi and my Pyramid application. uwsgi normally uses duplicate keys, but Python 3's ConfigParser rejects duplicate keys unless passed strict=False. For example, this will work in Python 2 but fail in Python 3.

[uwsgi]
env=VARIABLE1=a
env=VARIABLE2=b

[app:main]
use = egg:bongo#whisky

Should it be easier to pass strict=False to the ConfigParser that eventually gets called from pyramid.paster.get_app()?

Since Python 3.2 and newer, the ConfigParser standard library now defaults to "strict=True" when processing .ini files.
This change does not allow duplicate key values in an .ini file.
This causes web applications that use uWSGI some headache, since some uWSGI features, like having multiple spooler directories be defined as duplicate keys in an .ini file. uWSGI has their own internal parser for .ini files (which is also very liberal in their idea of .ini "rules").

In looking at PasteDeploy's code, I can't find a way to "pass in" the needed "strict=False" argument to NiceConfigParser's constructor/init() function.

Steps to reproduce the behavior:

• Create an .ini file with a duplicate key value in any section.

I'm mostly asking 2 questions:

1. Is there a way to pass the needed argument to the NiceConfigParser init() function via the loadapp() function? (I'm not seeing how any extra keyword arguments would be funneled to that function)
2. if not, then is are there suggestions on how to approach this? (e.g. I could monkey_patch the init() function in ConfigLoader in loadwsgi.py)

setup.py reports bad information with regard to supported python versions and location of the code

Pastedeploy uses setuptools, but it's not mentioned in install_requires in setup.py

Bug Report

On page https://pypi.org/project/PasteDeploy/ in Project links section "Documentation" link leads to https://docs.pylonsproject.org/projects/pastedeploy/en/latest/ which produces HTTP 404 error.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://pypi.org/project/PasteDeploy/
2. Click on Documentation
3. See error 404

Expected behavior
Some kind of documentation

Screenshots

The current docs at https://pastedeploy.readthedocs.io/en/latest/ are out of date and we lack access to update them. We'd like to republish them elsewhere.

see Pylons/pyramid#3425 (comment) with:

I think the best solution here would be to bring PasteDeploy under the pylons project and we'll give it a url in the docs.pylonsproject.org namespace

Pylons Project projects use a contributing.md that informs users how to contribute. GitHub uses it to automatically inform newbies of the contributing policy when opening a new issue or PR. Do you want one added? Sample: https://github.com/Pylons/docs-style-guide/blob/master/contributing.md

I'm happy to make a PR.

Example: https://github.com/Pylons/docs-style-guide/blob/master/tox.ini#L5 and subsequent stanzas.

I'm happy to make a PR.

Pylons Project uses GitHub issue templates. Demo: https://github.com/Pylons/docs-style-guide/issues/new/choose

Do you want them added? I'm happy to make a PR.

Does pastedeploy have a license? GitHub will automatically recognize a LICENSE.txt file.

We need a Webhook for RTD to automatically build the docs, now that "Integrations & services" is deprecated. I'll look into this.

The stable branch build failed. Stuff from latest on RTD (master on GitHub) needs backporting.

The latest branch succeeded.

@cdent I'm not sure how you manage branches. Now is a good time to set a policy and communicate that. We communicate that in the contributing.md file. Please let me know.

According to this issue:
pypi/warehouse#4809 (comment)

It looks like you might have used python setup.py upload (which is now deprecated) instead of using twine, which caused some of the newer metadata fields to not be included in the upload.

Compare URLs between Pyramid with PasteDeploy on PyPI.

Some proxies are using the Forwarded HTTP header instead of the X-Forwarded-* headers.

For example, an OpenShift router would add only those headers:

Forwarded: for=?.?.?.?;host=myhost.example.com;proto=https;proto-version=h2
X-Forwarded-Port: 443
X-Forwarded-Proto-Version: h2

The header is described there: https://tools.ietf.org/html/rfc7239#section-4

It would be nice if the paste.deploy.config.PrefixMiddleware could support this header.

It would be nice to keep PyPI releases and git tags in sync :)