Trying out 0.8-dev (plugins branch on github)

[Sean Davis]

Hi, Doug.

Let me add to the list of thanks for picking up blogofile.  I am starting to play with the 0.8-dev version (plugins branch) from github.  I am working from the EnigmaCurry repository.  Is that the correct place from which to follow development, report issues, and make pull requests?  I have a few issues that have come up and I am not sure what are local issues (I am running into several layers of unicode problems) and what are issues that simply have not yet been addressed in the code.  What is the status of the plugins branch with regard to python version support (thanks for fixing the setup stuff for python 2.x), OS testing (I am typically developing on a Mac, known to behave differently with regard to encoding), and general stability/testing of the current codebase?  I want to report problems that I find, but if things are not supposed to work, then I will hold off a bit more on testing, etc.  

Again, I really appreciate you taking the project under your wing and look forward to using (and contributing where I can) to its success.

Thanks,

Sean

[Doug Latornell]

On Fri, Jun 1, 2012 at 12:14 PM, Sean Davis <sean...@gmail.com> wrote:
> Hi, Doug.
>
> Let me add to the list of thanks for picking up blogofile.

Thanks for the support!

> I am starting to
> play with the 0.8-dev version (plugins branch) from github.  I am working
> from the EnigmaCurry repository.  Is that the correct place from which to
> follow development, report issues, and make pull requests?

Yes.

> I have a few
> issues that have come up and I am not sure what are local issues (I am
> running into several layers of unicode problems) and what are issues that
> simply have not yet been addressed in the code.

I'm sure that there are issues resulting from the codebase unification
I landed last week. And I'm not surprised the Unicode tops the list. I
suspected I was taking a risk, but I felt that lowering the barrier
for people who aren't yet dedicated to Python 3 was worth it.

> What is the status of the
> plugins branch with regard to python version support (thanks for fixing the
> setup stuff for python 2.x), OS testing (I am typically developing on a Mac,
> known to behave differently with regard to encoding),

It packages and deploys in a virtualenv without errors under Python
2.6, 2.7 and 3.2. I'm testing that regularly as I work - also on a
Mac. I also periodically build my own site <http://douglatornell.ca/>
with whatever is at the HEAD of my dev branch but I'm not sure that's
much of a challenge - especially on the Unicode front. I typically
only do that in one version of Python (usually 3.2, sometimes 2.7).

> and general stability/testing of the current codebase?

The test suite currently at HEAD of the plugin branch on github
doesn't work at all for me; i.e. all tests fail. The tests are all
full stack integration tests and the failure seems to be in the setup
rather than what the tests are supposed to be testing. I haven't dug
in to try to resolve that because I know that the refactoring and
development I'm doing is going to change things anyway. So, initially
I've relied on tox, the ad hoc testing described above, and help from
folks like you.

As I work, I'm adding unit tests, and will add integration tests where
appropriate. I'm hoping to land the first bit of that work this
weekend. It's some refactoring in the blogofile.main module, mostly
aimed at shifting the blogofile init process from the site_init zip
files to the blogofile_blog plugin (or other future plugins).

> I want to report problems that I
> find, but if things are not supposed to work, then I will hold off a bit
> more on testing, etc.

I'm trying to keep the plugin branch on github in the "supposed to
work" state, so yes, please, report problems and submit patches. Until
I have more confidence in the test suite though, I can't guarantee it
won't be a bumpy ride...

>
> Again, I really appreciate you taking the project under your wing and look
> forward to using (and contributing where I can) to its success.
>
> Thanks,
> Sean

You're welcome, and thank you for joining in to help.

Doug

[Sean Davis]

On Fri, Jun 1, 2012 at 4:02 PM, Doug Latornell <d...@douglatornell.ca> wrote:

On Fri, Jun 1, 2012 at 12:14 PM, Sean Davis <sean...@gmail.com> wrote:
> Hi, Doug.
>
> Let me add to the list of thanks for picking up blogofile.

Thanks for the support!

> I am starting to
> play with the 0.8-dev version (plugins branch) from github.  I am working
> from the EnigmaCurry repository.  Is that the correct place from which to
> follow development, report issues, and make pull requests?

Yes.

> I have a few
> issues that have come up and I am not sure what are local issues (I am
> running into several layers of unicode problems) and what are issues that
> simply have not yet been addressed in the code.

I'm sure that there are issues resulting from the codebase unification
I landed last week. And I'm not surprised the Unicode tops the list. I
suspected I was taking a risk, but I felt that lowering the barrier
for people who aren't yet dedicated to Python 3 was worth it.

Definitely.  For many of us in scientific fields, python 3 is a ways off for everyday use.

I have tried things in 2.7 (using simple_blog) and noted some problems with blogofile serve (https://github.com/EnigmaCurry/blogofile/pull/120 ).  If I can create constructive reports or patches, I'll definitely let you know.

Sean

 

>
> Again, I really appreciate you taking the project under your wing and look
> forward to using (and contributing where I can) to its success.
>
> Thanks,
> Sean

You're welcome, and thank you for joining in to help.

Doug

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

[Doug Latornell]

On Friday, June 1, 2012 2:06:19 PM UTC-7, Sean Davis wrote:

...

I have tried things in 2.7 (using simple_blog) and noted some problems with blogofile serve (https://github.com/EnigmaCurry/blogofile/pull/120 ).  If I can create constructive reports or patches, I'll definitely let you know.

Thanks for that Sean. It took a little more tweaking to get the server working under both 2 and 3, but I think it's there now - just pushed to github. At some point I'll have to loop back to server.py to clean up the imports with the six library, and add some tests.

[Sean Davis]

Thanks, Doug.  Sorry for the half-baked patch.

Sean