On Sun, Nov 30, 2014 at 10:25 AM, Donald Stufft wrote:
>
> On Nov 30, 2014, at 1:05 PM, Guido van Rossum wrote:
>
> I don't feel it's my job to accept or reject this PEP, but I do have an
> opinion.
>
>
> So here’s a question. If it’s not your job to accept or reject this PEP,
> whose is it? Thi
On Mon, Dec 1, 2014 at 5:48 PM, Francis Giraldeau <
francis.girald...@gmail.com> wrote:
> - On the C-API side: I did a horrible and silly function show_type() to
> run every Py*_Check() to determine the type of a PyObject *. What would be
> the sane way to do that?
Questions like this are better
On Mon, Dec 1, 2014 at 1:38 PM, Nathaniel Smith wrote:
> On Mon, Dec 1, 2014 at 4:06 AM, Guido van Rossum wrote:
> > On Sun, Nov 30, 2014 at 5:42 PM, Nathaniel Smith wrote:
> >>
> >> On Mon, Dec 1, 2014 at 1:27 AM, Guido van Rossum
> wrote:
> >> > Nathaniel, did you look at Brett's LazyLoader?
Here is a working prototype for CPython to record all function call/return
using LTTng-UST, a fast tracer.
https://github.com/giraldeau/python-profile-ust
However, there are few issues and questions:
- I was not able to get PyTrace_EXCEPTION using "raise" or other error
conditions. How can we tr
On Mon, Dec 1, 2014 at 4:06 AM, Guido van Rossum wrote:
> On Sun, Nov 30, 2014 at 5:42 PM, Nathaniel Smith wrote:
>>
>> On Mon, Dec 1, 2014 at 1:27 AM, Guido van Rossum wrote:
>> > Nathaniel, did you look at Brett's LazyLoader? It overcomes the subclass
>> > issue by using a module loader that m
On Mon, Dec 01, 2014 at 03:52:21PM -0500, Terry Reedy wrote:
> On 12/1/2014 11:42 AM, Wes Turner wrote:
> >Is there an issue ticket or a wiki page that supports
>
> https://wiki.python.org/moin/
>
> >Markdown/ReStructuredText,
>
> whoops, I am not sure what moin uses.
Let's see...
https://
On 12/1/2014 11:42 AM, Wes Turner wrote:
Here's a roundup of tools links, to make sure we're all on the same page:
Git HG Rosetta Stone
===
https://github.com/sympy/sympy/wiki/Git-hg-rosetta-stone#rosetta-stone
BugWarrior
===
BugWarrior works with many issue tracker APIs
Hi!
On Mon, Dec 01, 2014 at 10:42:16AM -0600, Wes Turner
wrote:
> Here's a roundup of tools links, to make sure we're all on the same page:
Very nice!
> Is there an issue ticket or a wiki page that supports
> Markdown/ReStructuredText,
> where I could put this? Which URI do we assign to thi
> hg vs Github
At best, this is apples to oranges in comparing a DVCS to a platform,
or was the intention to change the subject to "hg vs git"? If so, then
it's promoting a developer tool war in the same vein as the never
ending vim vs emacs and will likely only result in continued
dissension. IMH
On Mon, Dec 1, 2014 at 12:37 PM, Jim J. Jewett wrote:
> I think even the proponents concede that git isn't better enough
> to justify a switch in repositories.
There are also many who find the Bitbucket tools more usable than the
Github tools.
I'm not aware of any functional differences (though
M. Cepl asked:
> What I really don't understand is why this discussion is hg v.
> GitHub, when it should be hg v. git. Particular hosting is
> a secondary issue
I think even the proponents concede that git isn't better enough
to justify a switch in repositories.
They do claim that GitHub (
On 12/01/2014 08:42 AM, Wes Turner wrote:
>
> Here's a roundup of tools links, to make sure we're all on the same page:
Thanks!
--
~Ethan~
signature.asc
Description: OpenPGP digital signature
___
Python-Dev mailing list
Python-Dev@python.org
https://
On 12/01/2014 01:05 PM, Matěj Cepl wrote:
> On 2014-12-01, 07:43 GMT, Donald Stufft wrote:
>>> I do not choose tools simply because they are written in
>>> Python -- I choose them because, being written in Python, I
>>> I can work on them if I need to: I can enhance them, I can
>>> fix them, I ca
Here's a roundup of tools links, to make sure we're all on the same page:
Git HG Rosetta Stone
===
https://github.com/sympy/sympy/wiki/Git-hg-rosetta-stone#rosetta-stone
BugWarrior
===
BugWarrior works with many issue tracker APIs
https://warehouse.python.org/project/bugw
On 2014-12-01, 07:43 GMT, Donald Stufft wrote:
>> I do not choose tools simply because they are written in
>> Python -- I choose them because, being written in Python, I
>> I can work on them if I need to: I can enhance them, I can
>> fix them, I can learn from them.
>
> Git uses the idea of smal
As far as I'm concerned I'm just waiting for your decision now.
On Mon, Dec 1, 2014 at 7:07 AM, Brett Cannon wrote:
>
>
> On Sun Nov 30 2014 at 8:25:25 PM Guido van Rossum
> wrote:
>
>> Can we please stop the hg-vs-git discussion? We've established earlier
>> that the capabilities of the DVCS i
On Sun Nov 30 2014 at 8:25:25 PM Guido van Rossum wrote:
> Can we please stop the hg-vs-git discussion? We've established earlier
> that the capabilities of the DVCS itself (hg or git) are not a
> differentiator, and further he-said-she-said isn't going to change
> anybody's opinion.
>
+1 from m
On Mon, Dec 1, 2014 at 12:25 AM, Ethan Furman wrote:
> One argument that keeps coming up is transferability of knowledge:
> knowing git and/or GitHub, as many seem to, it
> therefore becomes easier to commit to the Python ecosystem.
>
> What about the transferability of Python knowledge? Because
On Dec 01, 2014, at 03:54 PM, Chris Angelico wrote:
>In response to Guido's call for volunteers, I'm offering myself as a
>PEP editor. Who is in charge of this kind of thing? Who manages public
>key lists etc?
I can add you to the pep editors mailing list. Please send me a off-list
message with
On Tue, Dec 02, 2014 at 12:37:22AM +1100, Steven D'Aprano wrote:
[...]
> It's one thing to say that using hg is discouraging contributors, and
> that hg is much more popular.
/s/more/less/
--
Steven
___
Python-Dev mailing list
Python-Dev@python.org
On Sun, Nov 30, 2014 at 02:56:22PM -0500, Donald Stufft wrote:
> As I mentioned in my other email, we’re already supporting two
> different tools, and it’s a hope of mine to use this as a sort of
> testbed to moving the other repositories as well.
If we go down this path, can we have some *conc
On Mon, 1 Dec 2014 08:46:46 +0100
Matěj Cepl wrote:
> On 2014-12-01, 02:12 GMT, Pierre-Yves David wrote:
> > Migrating the DVCS content is usually easy.
>
> This is lovely mantra, but do you speak from your own
> experience? I did move rope from Bitbucket to
> https://github.com/python-rope an
On 2014-12-01, 00:50 GMT, Donald Stufft wrote:
> The only thing that is true is that git users are more likely to use the
> ability to rewrite history than Mercurial users are, but you’ll typically
> find that people generally don’t do this on public branches, only on private
> branches.
And I wou
On 2014-12-01, 02:12 GMT, Pierre-Yves David wrote:
> Migrating the DVCS content is usually easy.
This is lovely mantra, but do you speak from your own
experience? I did move rope from Bitbucket to
https://github.com/python-rope and it was A LOT of work
(particularly issues, existing pull reques
On 2014-11-30, 11:18 GMT, Ben Finney wrote:
> Donald Stufft writes:
>
>> I think there is a big difference here between using a closed source
>> VCS or compiler and using a closed source code host. Namely in that
>> the protocol is defined by git so switching from one host to another
>> is easy.
>
On Sun, 30 Nov 2014 22:06:03 -0500
Terry Reedy wrote:
>
> If the mirror experiment is successful, the devguide might be the next
> experiment. It does not have any one maintainer, and *is* tied to the
> tracker. But herein lies the problem with the devguide. There are 22
> issues, down just
26 matches
Mail list logo
