[py3porters-devel] [Piuparts-devel] [Needs Port] piuparts.debian.org

[Paul Tagliamonte]

We should file + take bugs, or use a wiki page or something.

Good point! Let's start with wiki. I'm about to start filing some bugs now.

Cheers,
  Paul

On Sun, Apr 19, 2015 at 11:10 AM, Johannes <ichhabekeineemail at gmx.net> wrote:
> Is there any place where it's coordinated who is working on which project?
> Maybe a Wiki or better some kind like a company on github?
>
> bg,
> Johannes
>
>
> On 19.04.2015 14:42, Bernhard Janetzki wrote:
>>>
>>> On 19 Apr 2015, at 14:30, Holger Levsen <holger at layer-acht.org> wrote:
>>>
>>> With tox you can test agains multiple python versions. You define the
>>>>
>>>> versions you want to test agains in a file called “tox.ini". Instead of
>>>> calling “nosetests" you call the command “tox” which, in our case, calls
>>>> nosetests with py34 and py27.
>>>
>>>
>>> cool! Looking forward to the patch :)
>>>
>>>> https://github.com/ierror/piuparts/blob/develop/tox.ini
>>>
>>>
>>> because I only see aa6e5865 in that branch, and that had "WIP" in the
>>> commit
>>> message, so I didnt consider it. Please do send a specific patch for this
>>> feature.
>>>
>>>> I think to start with a new py3 branch on your side is the way to go.
>>>
>>>
>>> well, please just do it. Start from a fresh develop branch…
>>
>>
>> Do i need to create a patchfile and send it to the list or should i send
>> specific commits you can merge?
>> Thank you for guiding me, the dev process here is new to me :)
>>
>> --
>> kid: 99C3C059
>> fpr: 90E7 F356 3F9D 6595 616F  9068 DE13 283B 99C3 C059
>>
>>
>>
>> _______________________________________________
>> py3porters-devel mailing list
>> py3porters-devel at lists.alioth.debian.org
>> https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel
>>
>
>
> _______________________________________________
> py3porters-devel mailing list
> py3porters-devel at lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel



-- 
:wq