[pylons-devel] Read the Docs GitHub Services Deprecation and replacement with Webhooks

[Steve Piercy]

Howdy,

Read the Docs recently sent out the following message to Admins 
of sub-projects under the Pylons Project:


=== begin ===
Your project, , is currently using GitHub Services 
to trigger builds on Read the Docs. Effective January 31, 2019, 
GitHub will no longer process requests using the Services 
feature, and so Read the Docs will not receive notifications on 
updates to your repository.


To continue building your Read the Docs project on changes to 
your repository, you will need to add a new webhook on your 
GitHub repository. You can either connect your GitHub account 
and configure a GitHub webhook integration, or you can add a 
generic webhook integration.


You can find more information on our webhook intergrations in 
our documentation, at:


https://docs.readthedocs.io/en/latest/webhooks.html#webhook-github-services
===  end  ===

The following projects have been updated by Pylons core team 
members to use Webhooks for Read the Docs:


deform
docs-style-guide
Pyramid
pyramid_beaker
pyramid_chameleon
pyramid_cookbook
pyramid_debugtoolbar
pyramid_tm
pyramid_tutorials
pyramid_zcml
pyramid-blogr
waitress
WebOb
zodburi

The following projects that are also listed on Read the Docs as 
sub-projects under Pylons might have been updated to use GitHub 
Webhooks.  I have not checked them.  I suggest you verify that 
the Webhook for your project is in fact working.


acidfs
akhet
Churro
colander
hupper
Jove
jslibs
peppercorn
plaster
pylons
pylons-pastedeploy
pylons-webframework
pyramid_amon
pyramid_deform
pyramid_errmail
pyramid_exclog
pyramid_formish
pyramid_handlers
pyramid_jinja2
pyramid_jqm
pyramid_layout
pyramid_ldap
pyramid_mailer
pyramid_mako
pyramid_nacl_session
pyramid_retry
pyramid_rpc
pyramid_simpleform
pyramid_traversalwrapper
pyramid_who
pyramid_xmlrpc
pyramid_zodbconn
repozitory
SQLAHelper
Sub Projects
substanced
translationstring
venusian
WebHelpers
WebTest

--steve


Steve Piercy, Eugene, OR

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] Make Pyramid 1.7 scaffolds ready for naïve usage of py.test and tox in new projects?

[Steve Piercy]

It's hard to miss contributing.md.  When you create a new issue 
or PR, a friendly yellow bar appears with the message:


Please review the [guidelines for 
contributing](https://github.com/Pylons/pyramid/issues/new) to 
this repository.


www.pylonsproject.org is limping along.  It's on the list of 
to-dos, behind the [new marketing site for 
Pyramid](https://trypyramid.com) and a new Sphinx theme for documentation.


https://github.com/Pylons/trypyramid.com
https://github.com/Pylons/pyramid-sphinx-themes
https://github.com/Pylons/pylonsproject.org

The branch to which you submit a PR should always be taken into 
consideration.  'master' is usually default.  We usually 
backport changes from master to a specific branch.


--steve


On 5/6/16 at 8:08 PM, vincent.fero...@gmail.com (Vincent 
Férotin) pronounced:



Ok, here's an attempt for the PR: https://github.com/Pylons/pyramid/pull/2545

Thank you for your patience, and thank you Steve for pointing me the
right document! I wasn't aware of its existence, as it seems not
integrated to HTML documentation (?). (I've previously found the
http://www.pylonsproject.org/community/how-to-contribute which is not
so helpful.)
As an aside, following steps GitHub Flow, I create new branch directly
from master, but was confused by the paragraph on other branches
(https://github.com/Pylons/pyramid/blob/master/contributing.md#git-branches):
should I have taken this in consideration?

Again, thank you Steve!

-- Vincent

2016-05-06 19:21 GMT+02:00 Steve Piercy :

We try to follow a good git workflow.[1]

The error provides instructions of what to do.


astuce: Pull distant changes (e.g. 'git pull ...')
astuce: before pushing. [...]").



Which implies you did not follow the helpful instructions in contributing.md
under "Building documentation for a Pylons Project project", steps 6-10[1]
which I wrote to prevent such occurrences.  I haz a sad.  :-(

[1] https://help.github.com/articles/what-is-a-good-git-workflow/
[2]


https://github.com/Pylons/pyramid/blob/master/contributing.md#building-
documentation-for-a-pylons-project-project


--steve



On 5/6/16 at 6:41 PM, vincent.fero...@gmail.com (Vincent Férotin)
pronounced:



I totally agree, Steve, that there is much more to explore with
py.test than simple invocation we describe here. And I better
understand how you come to the pattern ``py.test mymodule/mytests.py
-q``. My experience took an other path, where I was sure that using
``py.test`` alone should work, googled about it, and found
configuration i purposed here ;-)

@all:
Anyway, I rework previous patch to meet Michael preferences, and it is
now simpler: just adding tow new file to each scaffold (one for
`pytest`, the other for `coverage`). I also update narrative doc. to
first use simple ``py.test -q`` call (letting a reference to the more
explicit ``py.test mymodule/mytests.py -q`` pattern).

The bad news is that I simply failed to create a PR, in that pushing
new commits to 1.7-branch of my forked repo. aborts (with a
[french/here translated] message like:
" ! [rejected]1.7-branch -> 1.7-branch (non-fast-forward)
error: unable to push references to
'https://github.com/vincent-ferotin/pyramid.git'
astuce: Update failed due to branch head is behind
astuce: its distant homologue.
astuce: Pull distant changes (e.g. 'git pull ...')
astuce: before pushing. [...]").

I'm not familiar enough with git to resolve this issue.
So I push patches here: https://github.com/vincent-ferotin/pyramid-patches
Patches could be imported by StackedGit (`stg`) through ``stg import
--series pyramid-patches/series``).

I'm sorry about that, and hope this will not abort insert of these
changes in Pyramid's repo.

-- Vincent

2016-05-06 17:52 GMT+02:00 Steve Piercy :


In this case, py.test was totally new to me.  I had always used ``nose``
or
``tox`` that someone else wrote or setup.py'ed for me.  I was a beginner
to
py.test and test discoverability.

When I tried running tests out of the box following that pattern via
``py.test``, it didn't work.  Hmm, I thought, there *must* be some way to
make it work.  So I Google Fu'd, visited the link[1] to read about test
discovery, and it became clear in my mind how to do so.  I then wrote the
documentation for how to run tests for the scaffold.  As a beginner, I
managed to work it out.

Because I learned something from this process, I think it is good for
beginners to realize that there is more to py.test than its mere
invocation
without options.  There's a lot to explore.  After having this
discussion, I
think I should add this reference to the tutorial installation step.

For what it's worth, when we go deeper into tests, we use the simple
invocation with a single option to suppress output, ``py.test -q``.[2]

[1] http://pytest.org/latest/goodpractices.html#python-test-discovery
[2]





http://d

Re: [pylons-devel] Make Pyramid 1.7 scaffolds ready for naïve usage of py.test and tox in new projects?

[Steve Piercy]

We try to follow a good git workflow.[1]

The error provides instructions of what to do.


astuce: Pull distant changes (e.g. 'git pull ...')
astuce: before pushing. [...]").


Which implies you did not follow the helpful instructions in 
contributing.md under "Building documentation for a Pylons 
Project project", steps 6-10[1] which I wrote to prevent such 
occurrences.  I haz a sad.  :-(


[1] https://help.github.com/articles/what-is-a-good-git-workflow/
[2] 
https://github.com/Pylons/pyramid/blob/master/contributing.md#building-documentation-for-a-pylons-project-project

--steve



On 5/6/16 at 6:41 PM, vincent.fero...@gmail.com (Vincent 
Férotin) pronounced:



I totally agree, Steve, that there is much more to explore with
py.test than simple invocation we describe here. And I better
understand how you come to the pattern ``py.test mymodule/mytests.py
-q``. My experience took an other path, where I was sure that using
``py.test`` alone should work, googled about it, and found
configuration i purposed here ;-)

@all:
Anyway, I rework previous patch to meet Michael preferences, and it is
now simpler: just adding tow new file to each scaffold (one for
`pytest`, the other for `coverage`). I also update narrative doc. to
first use simple ``py.test -q`` call (letting a reference to the more
explicit ``py.test mymodule/mytests.py -q`` pattern).

The bad news is that I simply failed to create a PR, in that pushing
new commits to 1.7-branch of my forked repo. aborts (with a
[french/here translated] message like:
" ! [rejected]1.7-branch -> 1.7-branch (non-fast-forward)
error: unable to push references to
'https://github.com/vincent-ferotin/pyramid.git'
astuce: Update failed due to branch head is behind
astuce: its distant homologue.
astuce: Pull distant changes (e.g. 'git pull ...')
astuce: before pushing. [...]").

I'm not familiar enough with git to resolve this issue.
So I push patches here: https://github.com/vincent-ferotin/pyramid-patches
Patches could be imported by StackedGit (`stg`) through ``stg import
--series pyramid-patches/series``).

I'm sorry about that, and hope this will not abort insert of these
changes in Pyramid's repo.

-- Vincent

2016-05-06 17:52 GMT+02:00 Steve Piercy :

In this case, py.test was totally new to me.  I had always used ``nose`` or
``tox`` that someone else wrote or setup.py'ed for me.  I was a beginner to
py.test and test discoverability.

When I tried running tests out of the box following that pattern via
``py.test``, it didn't work.  Hmm, I thought, there *must* be some way to
make it work.  So I Google Fu'd, visited the link[1] to read about test
discovery, and it became clear in my mind how to do so.  I then wrote the
documentation for how to run tests for the scaffold.  As a beginner, I
managed to work it out.

Because I learned something from this process, I think it is good for
beginners to realize that there is more to py.test than its mere invocation
without options.  There's a lot to explore.  After having this discussion, I
think I should add this reference to the tutorial installation step.

For what it's worth, when we go deeper into tests, we use the simple
invocation with a single option to suppress output, ``py.test -q``.[2]

[1] http://pytest.org/latest/goodpractices.html#python-test-discovery
[2]


http://docs.pylonsproject.org/projects/pyramid/en/1.7-branch/tutorials/wiki2/
tests.html#running-the-tests


--steve


On 5/6/16 at 2:51 PM, vincent.fero...@gmail.com (Vincent Férotin)
pronounced:



Thank you, Michael and Steve, for the quick responses.

I will open a PR on github with changes to take in consideration what you
said.

@Steve:
Sure you can explicitly tell py.test to run a specific test module,
but the whole point of my suggestion is to not pass test module path
to py.test. It's the point of view of a beginner, not familiar with
Pyramid scaffolds nor py.test: isn't it easier/more convenient to only
run ``py.test`` at project's root directory, just after project
creation by scaffold, and get all tests collected by default?

-- Vincent

2016-05-05 19:46 GMT+02:00 Steve Piercy :


On 5/5/16 at 9:44 AM, vincent.fero...@gmail.com (Vincent Férotin)
pronounced:


scaffolds are not ready for naive usage of py.test by new comers to
Pyramid,
i.e. running ``py.test [--cov]`` at new project's root collects no
tests.




You are correct in that one cannot just naïvely run:

$ py.test [--cov]

py.test discovers tests in the following manner:
http://pytest.org/latest/goodpractices.html#python-test-discovery

By following the instructions for the SQLAlchemy + URL dispatch wiki
tutorial to get started:





http://docs.pylonsproject.org/projects/pyramid/en/1.7-branch/tutorials/wiki2/

installation.html



I can run the tests:

stevepi-mbp:tutorial stevepiercy$ $VENV/bin/py.test tutorial/tests.py -q
..
2 passed in 0.54 s

Re: [pylons-devel] Make Pyramid 1.7 scaffolds ready for naïve usage of py.test and tox in new projects?

[Steve Piercy]

In this case, py.test was totally new to me.  I had always used 
``nose`` or ``tox`` that someone else wrote or setup.py'ed for 
me.  I was a beginner to py.test and test discoverability.


When I tried running tests out of the box following that pattern 
via ``py.test``, it didn't work.  Hmm, I thought, there *must* 
be some way to make it work.  So I Google Fu'd, visited the 
link[1] to read about test discovery, and it became clear in my 
mind how to do so.  I then wrote the documentation for how to 
run tests for the scaffold.  As a beginner, I managed to work it out.


Because I learned something from this process, I think it is 
good for beginners to realize that there is more to py.test than 
its mere invocation without options.  There's a lot to explore.  
After having this discussion, I think I should add this 
reference to the tutorial installation step.


For what it's worth, when we go deeper into tests, we use the 
simple invocation with a single option to suppress output, 
``py.test -q``.[2]


[1] http://pytest.org/latest/goodpractices.html#python-test-discovery
[2] 
http://docs.pylonsproject.org/projects/pyramid/en/1.7-branch/tutorials/wiki2/tests.html#running-the-tests

--steve


On 5/6/16 at 2:51 PM, vincent.fero...@gmail.com (Vincent 
Férotin) pronounced:



Thank you, Michael and Steve, for the quick responses.

I will open a PR on github with changes to take in consideration what you said.

@Steve:
Sure you can explicitly tell py.test to run a specific test module,
but the whole point of my suggestion is to not pass test module path
to py.test. It's the point of view of a beginner, not familiar with
Pyramid scaffolds nor py.test: isn't it easier/more convenient to only
run ``py.test`` at project's root directory, just after project
creation by scaffold, and get all tests collected by default?

-- Vincent

2016-05-05 19:46 GMT+02:00 Steve Piercy :

On 5/5/16 at 9:44 AM, vincent.fero...@gmail.com (Vincent Férotin)
pronounced:


scaffolds are not ready for naive usage of py.test by new comers to
Pyramid,
i.e. running ``py.test [--cov]`` at new project's root collects no tests.



You are correct in that one cannot just naïvely run:

$ py.test [--cov]

py.test discovers tests in the following manner:
http://pytest.org/latest/goodpractices.html#python-test-discovery

By following the instructions for the SQLAlchemy + URL dispatch wiki
tutorial to get started:


http://docs.pylonsproject.org/projects/pyramid/en/1.7-branch/tutorials/wiki2/
installation.html


I can run the tests:

stevepi-mbp:tutorial stevepiercy$ $VENV/bin/py.test tutorial/tests.py -q
..
2 passed in 0.54 seconds

stevepi-mbp:tutorial stevepiercy$ $VENV/bin/py.test --cov=tutorial
--cov-report=term-missing tutorial/tests.py
=== test
session starts

platform darwin -- Python 3.5.0, pytest-2.9.1, py-1.4.31, pluggy-0.3.1
rootdir: /Users/stevepiercy/pyramidtut/tutorial, inifile:
plugins: cov-2.2.1
collected 2 items

tutorial/tests.py ..
- coverage: platform
darwin, python 3.5.0-final-0
--
Name   Stmts   Miss  Cover   Missing

tutorial/__init__.py   8  625%   7-12
tutorial/models/__init__.py   22  0   100%
tutorial/models/meta.py5  0   100%
tutorial/models/mymodel.py 8  0   100%
tutorial/routes.py 3  3 0%   1-3
tutorial/scripts/__init__.py   0  0   100%
tutorial/scripts/initializedb.py  26 26 0%   1-45
tutorial/tests.py 39  0   100%
tutorial/views/__init__.py 0  0   100%
tutorial/views/default.py 12  0   100%
tutorial/views/notfound.py 4  4 0%   1-7

TOTAL127 3969%

= 2
passed in 0.57 seconds
=
stevepi-mbp:tutorial stevepiercy$

--steve


Steve Piercy, Soquel, CA


--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.





Steve Piercy, Soquel, CA

--
You received this message because you are su

Re: [pylons-devel] Make Pyramid 1.7 scaffolds ready for naïve usage of py.test and tox in new projects?

[Steve Piercy]

On 5/5/16 at 9:44 AM, vincent.fero...@gmail.com (Vincent 
Férotin) pronounced:



scaffolds are not ready for naive usage of py.test by new comers to Pyramid,
i.e. running ``py.test [--cov]`` at new project's root collects no tests.


You are correct in that one cannot just naïvely run:

$ py.test [--cov]

py.test discovers tests in the following manner:
http://pytest.org/latest/goodpractices.html#python-test-discovery

By following the instructions for the SQLAlchemy + URL dispatch 
wiki tutorial to get started:

http://docs.pylonsproject.org/projects/pyramid/en/1.7-branch/tutorials/wiki2/installation.html

I can run the tests:

stevepi-mbp:tutorial stevepiercy$ $VENV/bin/py.test 
tutorial/tests.py -q

..
2 passed in 0.54 seconds

stevepi-mbp:tutorial stevepiercy$ $VENV/bin/py.test 
--cov=tutorial --cov-report=term-missing tutorial/tests.py
=== 
test session starts 

platform darwin -- Python 3.5.0, pytest-2.9.1, py-1.4.31, pluggy-0.3.1
rootdir: /Users/stevepiercy/pyramidtut/tutorial, inifile:
plugins: cov-2.2.1
collected 2 items

tutorial/tests.py ..
- 
coverage: platform darwin, python 3.5.0-final-0 --

Name   Stmts   Miss  Cover   Missing

tutorial/__init__.py   8  625%   7-12
tutorial/models/__init__.py   22  0   100%
tutorial/models/meta.py5  0   100%
tutorial/models/mymodel.py 8  0   100%
tutorial/routes.py 3  3 0%   1-3
tutorial/scripts/__init__.py   0  0   100%
tutorial/scripts/initializedb.py  26 26 0%   1-45
tutorial/tests.py 39  0   100%
tutorial/views/__init__.py 0  0   100%
tutorial/views/default.py 12  0   100%
tutorial/views/notfound.py 4  4 0%   1-7

TOTAL127 3969%

= 
2 passed in 0.57 seconds =

stevepi-mbp:tutorial stevepiercy$

--steve


Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] weberror: Fix CSRF validation when token is unicode

[Steve Piercy]

I've also merged a PR to change the wording on this page to reflect reality.
http://www.pylonsproject.org/projects/pylons-framework/about

Soon it will be deployed.

--steve


On 2/9/16 at 6:50 AM, heyl...@gmail.com (Jan Heylen) pronounced:

> Great, thanks!
> 
> On Tue, Feb 9, 2016 at 1:11 AM, Bert JW Regeer  wrote:
> > I’ve just received push access to PyPi from Ben Bangert, will pull in that 
> > PR 
> and get a new release out that fixes the issue in the next day or so.
> >
> > Thanks,
> > Bert
> >
> >> On Feb 7, 2016, at 06:19, Jan Heylen  wrote:
> >>
> >> Hi,
> >>
> >> as user of the pylons web framework, I very much like the interactive 
> debugger, however, since some time, this is a broken feature.
> >>
> >> However, the fix (in weberror) is very trivial and already proposed as 
> >> pull 
> request by Patrick Valsecchi on github since November last year:
> >> Https://github.com/pylons/weberror/pull/11
> >>
> >> I know Pylons is no longer actively maintained, but the website does still 
> states: "The Pylons web framework 1.x line will continue to be maintained 
> alongside Pyramid" :-)
> >>
> >> Will this pull request be taken in and will weberror be updated in pypi? 
> Currently, this is still a version without this fix. 
> (https://pypi.python.org/pypi/WebError)
> >>
> >> Thanks,
> >>
> >> Jan Heylen
> >>
> >>
> >>
> >>
> >>
> >> --
> >> You received this message because you are subscribed to the Google Groups 
> "pylons-devel" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an 
> email to pylons-devel+unsubscr...@googlegroups.com.
> >> To post to this group, send email to pylons-devel@googlegroups.com.
> >> Visit this group at https://groups.google.com/group/pylons-devel.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > You received this message because you are subscribed to the Google Groups 
> "pylons-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> email to pylons-devel+unsubscr...@googlegroups.com.
> > To post to this group, send email to pylons-devel@googlegroups.com.
> > Visit this group at https://groups.google.com/group/pylons-devel.
> > For more options, visit https://groups.google.com/d/optout.
> 


Steve Piercy, Soquel, CA

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] Re: github pages for pylons project sites

[Steve Piercy]

What is the value for maintaining the domain name pylonshq.com?

The repos named pylonshq and pylonsrtd are rarely updated, 
typically only for releases of Pyramid, and will be superseded 
by the new repo pylonsproject.org.  Eventually both pylonshq and 
pylonsrtd repos will cease to exist.

https://github.com/Pylons/pylonsproject.org

--steve


On 1/4/16 at 9:57 PM, bla...@laflamme.org (Blaise Laflamme) pronounced:

Obviously the owner of pylonshq.com never pointed the site to 
the right address. If someone is able to reach him please tell 
him to point to the marketing.pylonsproject.org IP.



On Monday, January 4, 2016 at 1:10:36 PM UTC-5, Jonathan Vanasco wrote:


I just wanted to add that PylonsHQ redirects to PylonsProject 
(and is the name of the github project), and that link should 
be maintained.







Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

[pylons-devel] Additional Maintainers Needed for Pylons Project projects

[Steve Piercy]

Via @doughellmann for virtualenvwrapper:
https://doughellmann.com/blog/2016/01/03/virtualenvwrapper-needs-a-new-maintainer/

For those projects under the Pylons Project that need a new or 
additional active maintainer, this could serve as an example 
announcement to that effect.  An announcement creates a vacuum.


It would be good to have at least two active maintainers per 
project, to avoid the bus factor.


What do you maintainers think?

--steve

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Steve Piercy  Website Builder  Soquel, CA
   <http://www.StevePiercy.com/>

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] github pages for pylons project sites

[Steve Piercy]

OK, so we need to set that expectation in a contributing.md 
document for the repo.  We cannot assume that contributors know 
our process when it's not documented for a given repo.


GitHub uses contributing.md:
https://help.github.com/articles/setting-guidelines-for-repository-contributors/

Example from another Pylons Project:
https://github.com/Pylons/pyramid/blob/master/contributing.md

I've logged an issue for trypyramid.com:
https://github.com/Pylons/tpc/issues/35

--steve


On 1/2/16 at 1:33 PM, bla...@laflamme.org (Blaise Laflamme) pronounced:

Contributor should be able to compile and see their own changes 
before they submit PRs, and we should do the same when 
reviewing. The dev branch I was proposing earlier was to help 
us merging PR and make sure we don't publish unfinished work on master.


On Saturday, January 2, 2016 at 4:28:29 PM UTC-5, Steve Piercy wrote:


On 1/2/16 at 3:11 PM, mmer...@gmail.com  (Michael 
Merickel) pronounced:
Hey everyone, I'm starting the discussion (which I hope is 
very quick) about what to do with our public websites.

Right now we have:
- docs.pylonsproject.org (docs, hosted on rtd) - 
docs.pylonsproject.org/projects (hosted on rtd) - 
www.pylonsproject.org (ppo, hosted somewhere controlled by 
blaise/ben) - trypyramid.com (tpc, hosted somewhere I have no 
idea) - webob.org (hosted somewhere I have no idea) - 
docs.webob.org (hosted on rtd)

I think Blaise is the only person with access to DNS configurations but

I'm

not really sure.
I'd like to propose moving several sites over to github pages 
for easier management and update the DNS records with CNAME 
records to the github pages sites. All of the sites are 
static and it would allow master to be always live, as well 
as control deployment permissions via the standard 
github.com/Pylons membership levels.

The sites I'd like to see updated are:
- www.pylonsproject.org - trypyramid.com - webob.org
Can anyone give me a reason to not go this route?


+1, but with a concern for the non-doc/HTML-only/marketing 
sites.  How do we preview proposed changes with as much ease 
as deploying to a production environment?
Taking trypyramid.com as an example, I could set up a CNAME of 
trypyramid.stevepiercy.com, and point it at a particular 
branch of stevepiercy/tpc before submitting a PR to 
Pylons/tpc.  But this would raise a bar for new individual contributions.
Perhaps we declare a branch 'dev' or 'staging' for reviewing 
proposed changes, and set up a CNAME for each marketing website?

--steve
 Steve Piercy, Soquel, CA






Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] github pages for pylons project sites

[Steve Piercy]

On 1/2/16 at 3:11 PM, mmeri...@gmail.com (Michael Merickel) pronounced:


Hey everyone, I'm starting the discussion (which I hope is very quick)
about what to do with our public websites.

Right now we have:

- docs.pylonsproject.org (docs, hosted on rtd)
- docs.pylonsproject.org/projects (hosted on rtd)
- www.pylonsproject.org (ppo, hosted somewhere controlled by blaise/ben)
- trypyramid.com (tpc, hosted somewhere I have no idea)
- webob.org (hosted somewhere I have no idea)
- docs.webob.org (hosted on rtd)

I think Blaise is the only person with access to DNS configurations but I'm
not really sure.

I'd like to propose moving several sites over to github pages for easier
management and update the DNS records with CNAME records to the github
pages sites. All of the sites are static and it would allow master to be
always live, as well as control deployment permissions via the standard
github.com/Pylons membership levels.

The sites I'd like to see updated are:

- www.pylonsproject.org
- trypyramid.com
- webob.org

Can anyone give me a reason to not go this route?


+1, but with a concern for the non-doc/HTML-only/marketing 
sites.  How do we preview proposed changes with as much ease as 
deploying to a production environment?


Taking trypyramid.com as an example, I could set up a CNAME of 
trypyramid.stevepiercy.com, and point it at a particular branch 
of stevepiercy/tpc before submitting a PR to Pylons/tpc.  But 
this would raise a bar for new individual contributions.


Perhaps we declare a branch 'dev' or 'staging' for reviewing 
proposed changes, and set up a CNAME for each marketing website?


--steve


Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

[pylons-devel] PyCharm Open Source Licenses for Pylons Project

[Steve Piercy]

I have requested and received a limited number of free open 
source licenses for PyCharm to distribute to members of the 
Pylons Project.  If you satisfy the following requirements, you 
are eligible to request one of these licenses.


* Be an active committer who regularly contributes of the Pylons Project.
* Use PyCharm for the purpose of development of the Pylons 
Project's projects.

* Do not use PyCharm for any commercial purposes.
* Agree to the full license terms of PyCharm from JetBrains: 
https://www.jetbrains.com/buy/opensource/?product=pycharm#license-terms

Please send email to me off-list to make a request.

Additionally, if you previously had an open source license, 
JetBrains has changed its product licensing model from perpetual 
licenses to subscriptions.  This migration process may have led 
you to experience issues while converting your existing open 
source license to an open source subscription.  While the 
previous open source license was multi-user, the new 
subscriptions are distributed on a per-user basis.  Please send 
email to me off-list to make a request for a new license to 
resolve this issue.


Thank you to PyCharm for their continued support of the Pylons 
Project and open source software!  Read more information about PyCharm:

https://www.jetbrains.com/pycharm/

--steve


Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] Release process

[Steve Piercy]

AFAIK, there is no official roadmap in the traditional sense.  
Instead we use the issue tracker, and assign tickets to milestones.

https://github.com/Pylons/pyramid/issues
https://github.com/Pylons/pyramid/milestones

The release process is outlined in RELEASING.txt in the repo.
https://github.com/Pylons/pyramid/blob/master/RELEASING.txt

--steve


On 8/3/15 at 12:27 PM, richardt...@gmail.com (Ricardo 
d'Oliveira) pronounced:


Hello there, I'm writing a document for deciding which 
framework I'm going to use on my projects from then on, but I 
can't find Pyramid roadmap and release process, described with 
rich details such as Django is? Is there any document with 
Pyramid release process?




--------
Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] Re: Ecommerce platform based on Pyramid/Pylons

[Steve Piercy]

There are none.  There are probably many proprietary ecommerce 
apps written on top of Pyramid.


There are many application development environments built on top 
of Pyramid which may facilitate the creation of an ecommerce app.

http://docs.pylonsproject.org/en/latest/docs/pyramid.html#sample-pyramid-development-environments

There are maybe a half-dozen FOSS ecommerce apps written in 
Python using Plone and Django.


--steve


On 7/30/15 at 10:25 PM, pinak...@gmail.com (Ecommerce Platform 
Architect) pronounced:


Would really appreciate if someone could give me any pointers. 
I tried searching on the net but couldn't find any open source 
ecommerce framework on pyramid/pylons.


Thanks,
Pinakee

On Wednesday, July 29, 2015 at 2:09:47 PM UTC+5:30, Ecommerce 
Platform Architect wrote:


Hi,
I have been using Python based framework for quite sometime 
and have built social networking platform, CMS platform for 
Videos etc. using python frameworks.
Right now I am evaluating a platform for Ecommerce which is 
our company's next target. Hence, I was wondering if there's 
any open-source ecommerce platform built on Pyramid. For 
example Django has Oscar, Saleor etc. We could build the 
platform ground up but time to market is of essence. Hence, 
was looking for some already available modules/framework.


Would appreciate your help/response.

Thanks.




--------
Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] Pylons 1.x maintenance

[Steve Piercy]

On 7/20/15 at 6:10 PM, and...@shadura.me (Andrew Shadura) pronounced:


Hi,

On Jul 20, 2015 5:11 PM, "Steve Piercy"  wrote:

"Take over" implies ownership.  Is that what you mean?


I mean being able to react promptly to security and compatibility issues,
merge and review patches, tag and upload releases. The core team of
Kallithea has necessary skills and experience, so I think we can manage
providing Pylons all life support it needs :)


You could be added as a Core Developer so that you can manage pull

requests.

https://github.com/orgs/Pylons/teams/core-developers


After a brief chat in #pylons on irc.freenode.net, it was 
suggested that a new group, pylons-legacy or something like 
that, that has access only to the Pylons repo would be more appropriate.


To proceed, please contact Ben Bangert directly, as he is the 
owner of Pylons the web framework, and work out any details.  I 
don't have any say in the matter; I'm just facilitating.

https://github.com/bbangert

At the very least, you can always fork the project and maintain 
your fork, but I understand that you'd like to be a contributor 
to the core.



This, together with PyPI authorisation, would be useful.


You are more than welcome to make contributions to the code, following

the contribution guidelines.

http://www.pylonsproject.org/community/how-to-contribute


P.S. Please Cc me, as I'm not subscribed to the list, and for some reason
topic subscription didn't work either.


You are shown as a subscriber with "No email" as your 
preference.  Would you like me to change that?  Other options 
are "All email" and "Digest".  If you want to change it, you 
must have a Google Account for the address.


--steve


Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] Pylons 1.x maintenance

[Steve Piercy]

"Take over" implies ownership.  Is that what you mean?

You could be added as a Core Developer so that you can manage 
pull requests.

https://github.com/orgs/Pylons/teams/core-developers

You are more than welcome to make contributions to the code, 
following the contribution guidelines.

http://www.pylonsproject.org/community/how-to-contribute

--steve


On 7/19/15 at 1:21 PM, and...@shadura.me (Andrew Shadura) pronounced:


Hello everyone,

I'm one of the developers of Kallithea, a source code hosting and
review system, which is currently based on Pylons 1.0. As we're busy
polishing essential features of the software, we don't currently have
time or manpower to migrate to some less obsolete framework, so we
stick to Pylons. It happens we need certain things to be fixed in
Pylons, but it seems the old code doesn't receive much love these days
and it's not really well-maintained.

I wonder, what if we take over the maintenance of the project and so
that we can keep it more alive than it is currently? We'd really not
like to have our own fork of Pylons :)

[0] https://kallithea-scm.org/

--
Cheers,
Andrew




Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] Begginer Advice

[Steve Piercy]

Hi Bojan,

To begin learning Pyramid, here are some suggested resources.

This site shows you how to create a simple one-file Pyramid 
application.  More importantly, its navigation provides entry 
points to other resources for learning Pyramid.  I consider this 
page as my Pyramid home base.

http://trypyramid.com/

For a new person to Pyramid, I would recommend the Quick 
Tutorial.  It provides a comprehensive step-by-step introduction 
to the concepts of web applications, using Pyramid as the medium.

http://docs.pylonsproject.org/projects/pyramid/en/latest/quick_tutorial/index.html

When I'm ready to try something else, I go back to 
TryPyramid.com and pick something from the navigation.


As far as MVC, well, Pyramid does not fit well into that 
concept.  See:

http://docs.pylonsproject.org/projects/pyramid/en/latest/designdefense.html?highlight=mvc#pyramid-gets-its-terminology-wrong-mvc

--steve


On 11/25/14 at 6:12 AM, bste...@hotmail.com (Bojan Stepic) pronounced:

Hi everyone. I wanted to see if anyone would have advice on how 
to approach learning pyramid framework.I have solid knowledge 
of python and I am trying to branch out to using packages, 
modules, frameworks etc. I know that there is documentation 
provided on the pylons site, but for a person that is just 
starting with learning the MVC architecture it looks quite 
daunting. Any beginner level advice that you might share from 
your experiences? Thank you.





Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] static_url usage

[Steve Piercy]

Davide,

Would you like to add this to the Pyramid Cookbook?
http://docs.pylonsproject.org/projects/pyramid-cookbook/en/latest/

I am not sure under which category it would be placed.  We could 
start a new category, maybe "Developer Workflow Automation"?  
The default would be "Miscellaneous", but that wouldn't do 
justice to something I see becoming more commonplace in a 
developer's workflow.


Please let me know.

--steve


On 9/16/14 at 1:55 PM, davide.m...@gmail.com (davide moro) pronounced:


Hi,

thanks to your tips I've just published my first write up about
Pylons/Pyramid:
*
http://davidemoro.blogspot.com/2014/09/pyramid-starter-seed-yeomam-part-1.html

Thank you for your support,

davide


2014-08-17 23:55 GMT+02:00 davide moro :


Hi Michael!


2014-08-17 2:05 GMT+02:00 Michael Merickel :


You'll want to avoid changing the path in your usage of static_url.
Fortunately, Pyramid supports overriding static assets, so you can
make a dummy path and override that with your dev or production "real"
asset path.

config.add_static_view('images', 'p_started:webapp/images')
config.override_asset(to_override='p_started:webapp/images/',
override_with='p_started:webapp/dist/images')

request.static_url('p_started:webapp/images/pyramid.png')




Thank you, it works :)






Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] Re: Broken PDF link for 1.5 docs

[Steve Piercy]

On 5/17/14 at 10:35 PM, chr...@plope.com (Chris McDonough) pronounced:

> On 05/17/2014 10:28 PM, JohnWShipman wrote:
> >Still 404. Anybody? Bueller?
> 
> Please use
> http://media.readthedocs.org/pdf/pyramid/1.5-branch/pyramid.pdf . ReadTheDocs 
> doesn't much want to do what we tell it to do, so the "latest" PDF has been 
> moving 
> in and out of existence, AFAICT.

By following instructions to build your own HTML docs, you can build your own 
PDF.
https://github.com/Pylons/pyramid/blob/master/HACKING.txt#L201

I've also published a Dash docset for Pyramid.
https://github.com/Kapeli/Dash-User-Contributions/tree/master/docsets/Pyramid

More on the issue.
https://github.com/Pylons/pyramid/issues/1222#issuecomment-42795055

--steve



Steve Piercy, Soquel, CA

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-devel] Broken PDF link for 1.5 docs

[Steve Piercy]

https://github.com/Pylons/pyramid/issues/1222

I can build the PDF for the 1.5-branch locally, so this must still be a RTD 
issue.

--steve


On 5/6/14 at 8:07 PM, j...@nmt.edu (JohnWShipman) pronounced:

> On this page:
> 
> http://docs.pylonsproject.org/en/latest/docs/pyramid.html
> 
> there is a link with this text:
> 
> Pyramid latest 
> documentation<http://docs.pylonsproject.org/projects/pyramid/en/1.5-branch/>
>  (latest PDF <http://media.readthedocs.org/pdf/pyramid/latest/pyramid.pdf>) 
> 
> The URL it goes to is 404:
> 
> http://media.readthedocs.org/pdf/pyramid/latest/pyramid.pdf
> 
> Best regards,
> John W. Shipman, Web Developer, j...@nmt.edu
> National Radio Astronomy Observatories, Socorro, NM, USA
> 


Steve Piercy, Soquel, CA

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.

[pylons-devel] PyCharm 3 Open Source License

[Steve Piercy]

For those who are contributors to the Pylons Project or any of 
its subprojects and use PyCharm, PyCharm 3 Professional Edition 
accepts the Open Source License that works for PyCharm 2.7.3.


http://www.jetbrains.com/pycharm/

I'm also the keeper of the OSL for PyCharm.  Please contact me 
off-list for details.


--steve


Steve Piercy, Soquel, CA

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/groups/opt_out.

Re: some tests fail for pyramid_handlers 0.5

[Steve Piercy]

On 8/5/13 at 11:57 PM, h...@urpla.net (Hans-Peter Jansen) pronounced:

> Dear Chris,
> 
> don't know your favorite way to be informed about such issues:

https://github.com/Pylons/pyramid/issues

Ideally with a pull request that fixes it.  :D

Next favored would be here or in IRC.

--steve


> FYI, building on top of a fairly current pyramid stack, two tests of 
> pyramid_handlers fail:
> 
> [7s] + python setup.py nosetests --with-coverage
> [7s] running nosetests
> [7s] running egg_info
> [7s] writing requirements to pyramid_handlers.egg-info/requires.txt
> [7s] writing pyramid_handlers.egg-info/PKG-INFO
> [7s] writing top-level names to pyramid_handlers.egg-info/top_level.txt
> [7s] writing dependency_links to 
> pyramid_handlers.egg-info/dependency_links.txt
> [7s] writing entry points to pyramid_handlers.egg-info/entry_points.txt
> [7s] reading manifest file 'pyramid_handlers.egg-info/SOURCES.txt'
> [7s] writing manifest file 'pyramid_handlers.egg-info/SOURCES.txt'
> [7s] running build_ext
> [7s] E.E.
> [7s] 
> ==
> [7s] ERROR: test_it (pyramid_handlers.tests.TestHandlerDirective)
> [7s] 
> --
> [7s] Traceback (most recent call last):
> [7s]   File 
> "/home/abuild/rpmbuild/BUILD/pyramid_handlers-0.5/pyramid_handlers/tests.py", 
> line 
> 534, in test_it
> [7s] _execute_actions(actions)
> [7s]   File 
> "/home/abuild/rpmbuild/BUILD/pyramid_handlers-0.5/pyramid_handlers/tests.py", 
> line 
> 603, in _execute_actions
> [7s] action['callable']()
> [7s]   File "/usr/lib/python2.7/site-packages/pyramid/config/views.py", 
> line 
> 1165, in register
> [7s] order = view_intr['order']
> [7s] KeyError: 'order'
> [7s] 
> [7s] 
> ==
> [7s] ERROR: test_conflict_add_handler 
> (pyramid_handlers.tests.Test_add_handler)
> [7s] 
> --
> [7s] Traceback (most recent call last):
> [7s]   File 
> "/home/abuild/rpmbuild/BUILD/pyramid_handlers-0.5/pyramid_handlers/tests.py", 
> line 
> 408, in test_conflict_add_handler
> [7s] self.assertEqual(c[2], 'test_conflict_add_handler')
> [7s] IndexError: list index out of range
> [7s] 
> [7s] Name Stmts   Miss  Cover   Missing
> [7s] --
> [7s] pyramid_handlers   106  0   100%   
> [7s] pyramid_handlers.tests 475  499%   409, 535-538
> [7s] pyramid_handlers.zcml   26  0   100%   
> [7s] --
> [7s] TOTAL  607  499%   
> [7s] 
> --
> [7s] Ran 36 tests in 0.233s
> [7s] 
> [    7s] FAILED (errors=2)
> 
> Full build log is available here:
> https://build.opensuse.org/package/live_build_log/home:frispete:python/python-
> pyramid_handlers/openSUSE_12.2/x86_64
> 
> It also shows signs of the intersphinx issue reported an hour ago.
> 
> Cheers,
> Pete
> 


Steve Piercy, Soquel, CA

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/groups/opt_out.

Re: the Tools tab on the main site

[Steve Piercy]

I concur.  It's not directly relevant to the project, and the 
project does not receive any benefit for promoting these tools.


Although I also think there is an opportunity for sponsorship, 
e.g., where JetBrains provides Open Source Licenses for 
PyCharm.  It does this now for Pylons project contributors, and 
folks can contact me for details.


As another example, look at the sponsors and perks at Meetup groups.
http://www.meetup.com/PyLadiesSF/

--steve


On 4/5/13 at 11:07 PM, tshep...@gmail.com (Tshepang Lekhonkhobe) pronounced:


If you look at http://www.pylonsproject.org, you will notice there is
a tab named Tools, and all it points to is a list of pastebins. Seems
to me a forgotten corner, so I vote for removal.



--steve

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: choice of documentation license

[Steve Piercy]

On 3/22/13 at 4:32 PM, chr...@plope.com (Chris McDonough) pronounced:


On Fri, 2013-03-22 at 22:07 +0200, Tshepang Lekhonkhobe wrote:

Why choose a non-commercial license[1]? This has the disadvantage of
disallowing, for example, Debian to distribute it[2], which would be
nice.

[1]: http://creativecommons.org/licenses/by-nc-sa/3.0/
[2]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640780.



At this point I'd like to change the docs license to a free license,
TBH.  I had a delusion at some point that we'd need to protect it from
publishing shops that just scrape existing free docs and sell books
based on those docs without contributing anything back to the community,
which would compete with book sales from folks who do, but I think the
point is probably moot.  It would be easiest to give the docs the same
license as the code, I guess, although I'd be interested in hearing
other opinions.


So out of all these licenses:
http://creativecommons.org/licenses/

...are you suggesting this one would be the best fit?
http://creativecommons.org/licenses/by-sa/3.0/

--steve

--steve

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: license/copyright info at beginning of files

[Steve Piercy]

I reckon a reference to the copyright information would be 
sufficient, but the info itself would be too much.


--steve


On 3/22/13 at 9:59 PM, tshep...@gmail.com (Tshepang Lekhonkhobe) pronounced:


It is common practice to put licensing/copyright info at beginning of
files, but that info is missing on few of the files I looked at in
pyramid/ directory. Is it not an issue.

This question was prompted by my filing
https://github.com/Pylons/pyramid/pull/939, wondering if it's
necessary at all to even bother putting that info in setup.py.



--steve

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: use of "specified as" in documentation

[Steve Piercy]

IMO, "specified as" implies "must be" and it causes me to do a 
double-take.  "Supplied as" is a strange idiom and could be 
challenging to translate out of English.  I agree with your suggestion.


--steve



On 1/21/13 at 10:53 PM, tshep...@gmail.com (Tshepang 
Lekhonkhobe) pronounced:



As an example, given this piece of doc:

"render(renderer_name, value, request=None, package=None)"

As explanation would start with:

"Using the renderer specified as ``renderer_name``...".

I think this can be misleading at first to readers, as it was 
to me, that renderer_name is some special type of object, but 
is only a string. It is also overlong, and perhaps overly formal.
There are other variations of this, e.g. "supplied as". I think 
it would be better to simply change such sentences to say:


"Using the renderer ``renderer_name``..."

This is how CPython documentation does it and should therefore 
not be strange to Python users.


If this suggestion is acceptable, I will happily provide the patches.





--steve

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to 
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/pylons-devel?hl=en.

Re: Sites using Pyramid & Pyramid Advocacy

[Steve Piercy]

Also for the potential contributer who does not know how to 
contribute yet:

http://docs.pylonsproject.org/en/latest/#contributing

And:
http://docs.pylonsproject.org/en/latest/community/featuresbugs.html#working-on-code

Perhaps those should include mention of documentation or 
propaganda (marketing materials)?


--steve


On 10/23/12 at 12:48 PM, bla...@laflamme.org (Blaise Laflamme) pronounced:


In fact the site is at https://github.com/Pylons/pylonshq

pylonsrtd is the sphinx doc frontend for our full set of docs.

Best would probably be to collect them somewhere with logos in 
png+transparency at a good size, like 600px wide. I'll be 
sprinting o the new website at pylonsca on nov 12-13.


On Monday, 22 October 2012 20:13:56 UTC-4, Chris McDonough wrote:


On 10/22/2012 07:58 PM, Iain Duncan wrote:
Right, well I'll start collecting them then. Can you send it 
to idu...@xornot.com  ?




Chris, what's the easiest way for me to edit a page on the 
Pylons site to have a preamble and include my email address 
for people to send their links to?


The source of the site is on github.  I think this is it:
https://github.com/Pylons/pylonsrtd

- C



thanks Iain

On Sat, Oct 20, 2012 at 5:27 AM, Thomas G. Willis



> wrote:
I work for Batterii(http://batterii.com) we have a managed 
innovation solution written in pyramid and ember.js on top of 
google appengine. We actually have happy customers using it. 
I had sent someone our logo about a year ago for inclusion on 
the pylons site but it's still not up there.  Ember.js on the 
other hand included the logo fairly quickly.


On Friday, October 19, 2012 9:30:24 PM UTC-4, Blaise Laflamme wrote:
I think this should be added to the new pylons project / 
pyramid sites refactoring.

Noted.
If you have anything collected please share.
On Friday, 19 October 2012 17:33:15 UTC-4, Iain Duncan wrote:
Hi everyone, I started a thread about this ages ago, and 
expressed interest in making something happen, and then life 
happened and I had not time. Now I'm in a position where this 
has become a higher priority again. It seems to me that one 
thing really lacking in the Pyramid docs is some advocacy and 
examples of high profile sites using Pyramid. I realize this 
is a bit non-sensical in that we're not talking about a CMS, 
but I'm sure I'm far from the only one who has had a client 
ask about that.

Plone and SQLAlchemy have done a great job of it.
So questions: - sites using Pyramid? is there a list anywhere?
- If I want to help make one, what would be the recommended 
way of going about this?

--
You received this message because you are subscribed to the 
Google Groups "pylons-devel" group. To view this discussion 
on the web visit 
https://groups.google.com/d/msg/pylons-devel/-/sUw3kubem4EJ. 
To post to this group, send email to 
pylons...@googlegroups.com 
. To 
unsubscribe from this group, send email to 
pylons-devel...@googlegroups.com  
. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.









--steve

--
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to 
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/pylons-devel?hl=en.

Re: problem running helloworld

[Steve Piercy]

This one may be helpful too:
https://docs.pylonsproject.org/projects/pyramid_cookbook/dev/mac_install.html

You are welcome to update the instructions for 10.4.

--steve


On 8/31/11 at 11:21 PM, ja...@misterm.org (James Murty) pronounced:

> I have come across similar problems compiling Python libraries on OS
> X, caused by not having the "Mac OS X 10.4 Support" libraries
> installed (they're optional in X-Code) and by the Mac's version of GCC
> being incompatible with some code.
> 
> This blog post might give you some pointers:
> http://www.jamesmurty.com/2011/01/29/work-around-osx-lipo-figure-out-architecture-type
> /
> 
> FWIW a clean install on OS X 10.7 (Lion) caused no problems.
> 
> James
> 
> 
> On Aug 31, 11:41 am, Siddhartha Kasivajhula 
> wrote:
> > Hi all,
> > I'm new to Pyramid, and let me say first that it looks really cool and I've
> > been meaning to try it for a while :).
> > I was going through the documentation on installation and the hello world
> > app, and I ran into this error message while trying to run helloworld:
> >
> > siddhartha:apps-110-$python hellopyr.py
> > Traceback (most recent call last):
> >   File "hellopyr.py", line 2, in 
> >     from pyramid.configuration import Configurator
> >   File
> > "/Library/Python/2.6/site-packages/pyramid-1.0-py2.6.egg/pyramid/configurat 
> > ion.py",
> > line 1, in 
> >     from pyramid.config import Configurator as BaseConfigurator
> >   File
> > "/Library/Python/2.6/site-packages/pyramid-1.0-py2.6.egg/pyramid/config.py" 
> > ,
> > line 12, in 
> >     from zope.configuration.config import GroupingContextDecorator
> >   File
> > "/Library/Python/2.6/site-packages/zope.configuration-3.7.4-py2.6.egg/zope/ 
> configuration/config.py",
> > line 23, in 
> >     import zope.schema
> >   File
> > "/Library/Python/2.6/site-packages/zope.schema-3.8.0-py2.6.egg/zope/schema/ 
> __init__.py",
> > line 16, in 
> >     from zope.schema._field import Field, Container, Iterable, Orderable
> >   File
> > "/Library/Python/2.6/site-packages/zope.schema-3.8.0-py2.6.egg/zope/schema/ 
> _field.py",
> > line 24, in 
> >     from zope.interface import classImplements, implements, Interface
> > ImportError: No module named interface
> >
> > I installed virtualenv, my python version is:
> > $python --version
> > Python 2.6.1
> >
> > Looking back at the logs from 'bin/easy_install pyramid', I see this:
> >
> > Running zope.interface-3.7.0/setup.py -q bdist_egg --dist-dir
> > /var/folders/L6/L6RbbV+NGBaO6JGa905AKE+++TI/-Tmp-/easy_install-Zl0QT1/zope. 
> interface-3.7.0/egg-dist-tmp-gOf2zE
> > /usr/libexec/gcc/powerpc-apple-darwin10/4.2.1/as: assembler
> > (/usr/bin/../libexec/gcc/darwin/ppc/as or
> > /usr/bin/../local/libexec/gcc/darwin/ppc/as) for architecture ppc not
> > installed
> > Installed assemblers are:
> > /usr/bin/../libexec/gcc/darwin/x86_64/as for architecture x86_64
> > /usr/bin/../libexec/gcc/darwin/i386/as for architecture i386
> > src/zope/interface/_zope_interface_coptimizations.c:1676: fatal error: error
> > writing to -: Broken pipe
> > compilation terminated.
> > lipo: can't open input file:
> > /var/folders/L6/L6RbbV+NGBaO6JGa905AKE+++TI/-Tmp-//ccJe3vOi.out (No such
> > file or directory)
> > *** 
> > *
> > WARNING:
> >
> >         An optional code optimization (C extension) could not be compiled.
> >
> >         Optimizations for this package will not be available!
> >
> > command 'gcc-4.2' failed with exit status 1
> > *** 
> > *
> >
> > ...
> >
> > I also saw a few other messages like this but looks like it ultimately
> > completes the install successfully despite these warnings.
> >
> > Do you know what the problem may be?
> >
> > Thanks,
> > -Sid
> 

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to 
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/pylons-devel?hl=en.