Missing tags about python-textile HOT 28 CLOSED

Oh, and it would be nice if you guys @sebix and @ikirudennis could talk to each other who is now in charge of python-textile ;) (and then also upload a recent version to pypi - having many forks does not make a packager's life easier (I'm maintaining this package in Fedora)).

from python-textile.

Hi, @sebix. I wouldn't mind taking over python-textile on pypi. Truth be told, I've been thinking of rewriting the entire system. I just thought I was the only person using my fork, and hadn't felt like it was worth the time.

Anyway, If you're interested in transferring control of this, please let me know.
Thanks.

from python-textile.

Almost to the day two years ago, I took over the repository from chrisdrackett (after some commits from me updating test etc.) who had not enough time to keep the repo up to date. Now the history repeats itself. Sorry for that!

It would be great if you could maintain PyTextile on PyPi using your fork, or in the future, a rewrite.

from python-textile.

I'd like to echo what @thmo said. When I search the Internet, it's unclear what the canonical location of python-textile is. Also, who has upload rights for textile on PyPI? Is it @sebix or @ikirudennis or both?

I noticed that there is now a textile organization on GitHub started by a PHP textile project. Perhaps the official repository could be put under that organization with a group of maintainers like sebix, ikirudennis, and myself. @gocom, would you open to the addition of a Python textile implementation under the same umbrella?

I'd be happy to help with that migration and set up some stuff like Travis to ensure basic stuff works (e.g., Python 3 not blowing up on import).

from python-textile.

@ikirudennis is now the owner of the repository on pypi. He can now push his fork which is clearly ahead of my repo.

from python-textile.

@mblayman I myself have nothing against it and in my opinion the organisation could very well be used to host any Textile library repositories. The organisation's administration is up to @netcarver; holla Steve if you want your very own a repository under the organisation. @netcarver it's fine to you too?

from python-textile.

Jason Garber (Redcloth) and I created the textile organisation as a place to house (eventually) any implementation that wants a common umbrella location and to allow for the possible future development and publication of a textile standard and a set of compliance tests. Whilst a start has been made towards that goal, only the php-textile implementation that I forked from Textpattern a few years ago has gone under the umbrella so far - thanks to @gocom's help in preparing it for the move. I'm therefore very happy to create a repo for your python based textile project under the textile organisation.

Shall I create it as 'python-textile' or would you prefer a different repo name? (I don't know if there is more than one python implementation. If there is, you might want to use the repo name to differentiate it from the others - let me know.) Once the naming is sorted out, it sounds like I need to be adding @mblayman, @sebix and @ikirudennis as team members with write permissions - who do you want to give admin rights to?

from python-textile.

I think python-textile is the most logical name considering the project's history. Before creating a new project under the organization, I think @ikirudennis would need to agree since he is the current maintainer and person with upload rights to https://pypi.python.org/pypi/textile. I am only a consumer of the library that got confused about where the source code was because of the various Google results.

Also, if this change occurs, then it should probably follow the recommended steps suggested by the GitHub staff at https://help.github.com/articles/how-to-transfer-a-repository.

Thanks for your willingness to consider this addition to the textile organization.

from python-textile.

Transfering the repository @sebix / python-textile to the @textile organization is indeed a good idea. I could transfer the original repository to the organization, then all forks would point to the first repo of the organization and everything is fine.

from python-textile.

@sebix. Ok, I've created a start-up team called "python-textile folks" with just you in it (for now) but you should be able to add the other collaborators (let me know if you can't.) Once you initiate the transfer or the original repo to the textile organisation I'll then give the team access to it and then, I think, I should be out of the loop.

from python-textile.

Since @ikirudennis is the maintainer, should the transfer come from his repo instead? Or would it better to use @sebix's repo and merge @ikirudennis's work into the new organization owned repo? The sebix repo did not pass its tested when I cloned and ran it under Python 3, but the ikirudennis repo did pass the tests.

from python-textile.

Apologies for the delay. I was away for the weekend and am finally back and connected to the internet. And I've only been able to skim through all of these responses so far. Here are my thoughts:

I'm still trying to catch myself up on what I have to do and where (github, pypi and my local repositories). How about for the time being, we go ahead more or less as though the repository is just changing ownership from @sebix to me. I'll see if I can upload my current version to pypi for consumption through that channel. After that's working, I'll start talking with @mblayman and @netcarver about moving things over to their setup. This may take a couple days for me to do.

If any of the above seems wrong or needlessly complicated, I'm open to suggestions.

from python-textile.

To clarify how I came to my suggestion:
I thought of transfering my repo (as opposed to the one of @ikirudennis) because all forks point to this one. Transfering the @ikirudennis fork to the collaboration would cause that the forks point to my repo, which would not be maintained in favour of the repo in the collaboration. Of course the current state of @ikirudennis' fork should be merged to the repo in @textile
@ikirudennis: Yes, you could upload now just your current fork to pypi? This should not break anything and there are a lot of improvements included.

from python-textile.

I've just uploaded it to pypi, but in my brief testing, it doesn't seem like it's downloading the latest version. (This is my first project on pypi, so I'm not entirely sure if I've done everything correctly.) Would anyone be willing to test this for me?

I've got it squared away now. pypi has the latest and greatest 2.1.8

from python-textile.

I can test it. My project was crashing with the old version available on
pypi. I can check if it passes on python 3 now (which is something that
your repo was able to do based on my running of the tests).
On May 27, 2014 10:53 AM, "Dennis Burke" [email protected] wrote:

I've just uploaded it to pypi, but in my brief testing, it doesn't seem
like it's downloading the latest version. (This is my first project on
pypi, so I'm not entirely sure if I've done everything correctly.) Would
anyone be willing to test this for me?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-44286940
.

from python-textile.

Ah, oops. I didn't see the strike out text when I looked at my email. I can add a secondary confirmation that the new package is uploaded and works now.

from python-textile.

I spoke too soon. Textile failed on Python 3.2 https://travis-ci.org/mblayman/handroll/jobs/26176485. I know this link is from my project, but it's pretty clear that the failure is from textile's import.

from python-textile.

My memory is a little hazy on this, but here are the bits I'm remembering. When I started making changes to include support for py3k, I ran into trouble with 3.2 that I didn't run into with 3.3 and upward. I believe that's why the README says it supports 3.3+

I'll see if I can find any documentation to support that half-remembered brainfart though.

I'm guessing that upgrading to python 3.3+ would be too much to ask? (That's an honest question not a dickish "you're holding the phone wrong" response)

from python-textile.

My goal was to cover as many versions of Python as reasonable. Maybe it is unreasonable to try and include 3.2 as well. Mostly, I did it because Travis gave me an easy option to try it out.

Do you know if it's a crazy amount of work to support it? I see that the code uses the u'' syntax which was only re-introduced in 3.3. Was that the bulk of the difference or was there something else that was major?

I'm trying to gauge if it is worth me making a pull request to add the support for 3.2.

from python-textile.

I was in the middle of typing a response to explain it with a link to the PEP that defines it and other corroborating evidence... mostly just so I could have a record of the what and why. (Ironically, I had to waste some time looking up the Markdown syntax for creating links, and that's why you beat me to the punch. If I were using Textile... well, you probably would have beat me anyway.)

What it boils down to is that you're correct. The main reason why I skipped 3.2 was because being able to just say "the github repo covers 2.6+ and 3.3+" was easier than trying to maintain changes in different branches for each version. It's easy to make the changes to support 3.2, and we can utilize the power of pypi to do the nuts-and-bolts work to more easily support different versions. However, I'm a total n00b at this and the difficulty level goes up slightly. Please bear with me.

from python-textile.

Hi folks, nice to see all the communication and movement :) Thanks for that.

What is missing now, is the final consolidation into one definite repo and bugtracker - I'd like to know where to report failing tests and other things.

I lilke @mblayman's idea of putting the repository under the textile organization.

from python-textile.

The open question is which repository to move to the @textile organization, mine, or @ikirudennis' fork
My thouhgts on this can be found above. So I'm waiting for others' opinions.

from python-textile.

@sebix, I think you should go for it and transfer your repo to textile (especially if your repo has nothing new in it compared to @ikirudennis' fork). Then it should be a straightforward merge of his fork.

from python-textile.

I've just transferred the repository.

from python-textile.

I've now given the python-textile-folks team access to the repository. @sebix, @ikirudennis please could you both confirm you have access to the transferred repository - once that's done I'll remove myself from the team and I should be out of the python-textile loop.

from python-textile.

I just pushed a change.

from python-textile.

@ikirudennis, @sebix I've removed myself from your group. Hope all goes well with your newly 'homed' textile repo!

from python-textile.

I pushed the missing tags also to textile/python-textile

from python-textile.