Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simply Simplates #527

Closed
wants to merge 1,983 commits into from
Closed

Simply Simplates #527

wants to merge 1,983 commits into from

Conversation

chadwhitacre
Copy link
Contributor

Closes #526.

techtonik and others added 30 commits June 14, 2015 23:31
The latter is just `python`, which is masking the `python3` executable
we're now referring to in Makefile.
This reverts commit 0f65508.

Conflicts:
	.travis.yml
Makes the quickstart quicker; closes #441.
This is where main.options.python had been coming from.
* update dependencies
* detect already being inside a virtualenv
* rename a bunch of build functions
* build.py now uses sys.executable instead of main.options.python
We stopped using it in #389, but failed to in fact remove it.
Closes #450.
alias `website` as `application` in `wsgi`
I ended up just configuring harness.client.website inline in the tests.
I think that makes sense, right?
This fixes an insufficient test for whether Aspen is already installed.
The text 'found' shows up in the traceback when
pkg_resources.get_distribution fails in aspen/__init__.py, and that's
the way in which build.py's `import aspen` fails once the Response
import in __init__.py is removed.

The fix here is to delegate to pip to check whether this or that library
is already installed, rather than trying to duplicate that functionality
ourselves.
The processor is so thin now, there's no sense having a separate mixin
for configuration.
@Changaco
Copy link
Member

Rebased on master.

I think the next step here is to move the Django and Flask bits to separate branches, because the plan is to put them in their own repos, not in aspen-core.

@pjz
Copy link
Contributor

pjz commented Mar 10, 2016

If you want to split them up now, might as well split them into their own repos; it's not that much more than putting them into branches - all the packaging work (new setup.py, build/test/CI/etc) will need to be done anyway.

@Changaco
Copy link
Member

I've pushed this branch to aspen-core.py.

@Changaco Changaco closed this Mar 11, 2016
@Changaco Changaco deleted the just-simplates branch March 11, 2016 19:15
Changaco referenced this pull request in AspenWeb/aspen.py Mar 12, 2016
This change was originally made by whit537 in AspenWeb/aspen.py#527
@Changaco Changaco mentioned this pull request Mar 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants