Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Dec 1, 2014, at 1: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? Beca

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On 11/30/2014 03:41 PM, Terry Reedy wrote: > On 11/30/2014 2:27 PM, Ethan Furman wrote: >> On 11/30/2014 11:15 AM, Guido van Rossum wrote: >>> On Sun, Nov 30, 2014 at 6:15 AM, Brett Cannon wrote: On Sat, Nov 29, 2014, 21:55 Guido van Rossum wrote: > > All the use cases seem to be about

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

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 I know Python, I can customize hg; because I know Python I

[Python-Dev] Joining the PEP Editors team

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? ChrisA ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/p

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

Ben Finney writes: > Whether that is a *problem* is a matter of debate, but the fact that > Git's common workflow commonly discards information that some consider > valuable, is a simple fact. It *was* a simple fact in git 0.99. Since the advent of reflogs (years ago), it is simply false. Wo

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

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 makes all modules instances of a > > (trivial) Module subclass. I

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 07:43 PM, Donald Stufft wrote: The idea that unless Python as a project always picks something written in Python over something written in something else we’re somehow signaling to the world that if you want to write X kind of tool you should do it in some other language is lau

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 8:19 PM, Pierre-Yves David wrote: Mercurial have robust Windows support for a long time. This support is native (not using cygwin) and handle properly all kind of strange corner case. We have large scale ecosystem (http://unity3d.com/) using Mercurial on windows. We also have full

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 10:08 PM, Pierre-Yves David > wrote: > > > > On 11/29/2014 06:01 PM, Donald Stufft wrote: >> The reason the PEP primarily focuses on the popularity of the the tool is >> because as you mentioned, issues like poor documentation, bad support for a >> particular platform, a

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/29/2014 06:01 PM, Donald Stufft wrote: The reason the PEP primarily focuses on the popularity of the the tool is because as you mentioned, issues like poor documentation, bad support for a particular platform, a particular workflow not being very good can be solved by working with the too

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 4:45 PM, Donald Stufft wrote: I think you are stimulating more heated discussion than is necessary by trying to do too much, both in terms of physical changes and in terms of opinion persuasion. I am reminded of the integer division change. The initial discussion was initially

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, Nov 30, 2014 at 8:09 PM, Pierre-Yves David < pierre-yves.da...@ens-lyon.org> wrote: > > > On 11/30/2014 08:44 AM, Brett Cannon wrote: > >> For me personally, if I knew a simple patch integrated cleanly and >> passed on at least one buildbot -- when it wasn't a platform-specific >> fix -- t

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 09:09 AM, Donald Stufft wrote: Even converting between two FLOSS tools is an amazing amount of work. Look at >what Eric Raymond did with reposurgeon to convert from Bazaar to git. I fail to see how this is a reasonable argument to make at all since, as you mentioned, converting

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/29/2014 05:15 PM, Chris Angelico wrote: On Sun, Nov 30, 2014 at 11:37 AM, Donald Stufft wrote: I also don’t know how to do this. When I’m doing multiple things for CPython my “branching” strategy is essentially using hg diff to create a patch file with my “branch” name (``hg diff > my-b

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 08:30 AM, Donald Stufft wrote: On Nov 30, 2014, at 2:08 AM, Larry Hastings mailto:la...@hastings.org>> wrote: On 11/29/2014 04:37 PM, Donald Stufft wrote: On Nov 29, 2014, at 7:15 PM, Alex Gaynor wrote: Despite being a regular hg user for years, I have no idea how to create

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 08:44 AM, Brett Cannon wrote: For me personally, if I knew a simple patch integrated cleanly and passed on at least one buildbot -- when it wasn't a platform-specific fix -- then I could easily push a "Commit" button and be done with it (although this assumes single branch committ

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, Nov 30, 2014 at 6:44 PM, Donald Stufft wrote: > Yea this is essentially what I meant. We already have “unofficial” mirrors > for PEPs and CPython itself on Github that are updated a few times a day. > It wouldn’t be very difficult I think to make them official mirrors and > update them imm

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, Nov 30, 2014 at 6:40 PM, Donald Stufft wrote: > I’m not sure if it got lost in the discussion or if it was purposely left > out. However I did come up with another idea, where we enable people to make > PRs against these repositories with PR integration within roundup. Using the > fact tha

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 8:41 PM, Eric Snow wrote: > > On Sun, Nov 30, 2014 at 6:25 PM, Donald Stufft wrote: >> The technical benefits mostly come from Github generally being a higher >> quality product than it’s competitors, both FOSS and not. > > Here's a solution to allow contribution via PR w

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

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 makes all modules instances of a > (trivial) Module subclass. I'm sure this approach can be backported as far > as you need to go

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, Nov 30, 2014 at 6:25 PM, Donald Stufft wrote: >The technical benefits mostly come from Github generally being a higher > quality product than it’s competitors, both FOSS and not. Here's a solution to allow contribution via PR while not requiring anything to switch VCS or hosting: 1. Set

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 8:24 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. > > What's

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun, Nov 30, 2014 at 8:54 PM, Guido van Rossum wrote: > On Sun, Nov 30, 2014 at 11:29 AM, Nathaniel Smith wrote: >> >> On Sun, Nov 30, 2014 at 2:54 AM, Guido van Rossum >> wrote: >> > All the use cases seem to be about adding some kind of getattr hook to >> > modules. They all seem to involve

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 1 December 2014 01:17:02 CET, Ben Finney wrote: >Donald Stufft writes: > >> I have never heard of git losing history. > >In my experience talking with Git users about this problem, that >depends >on a very narrow definition of “losing history”. > >Git encourages re-writing, and thereby losin

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

Nathaniel, did you look at Brett's LazyLoader? It overcomes the subclass issue by using a module loader that makes all modules instances of a (trivial) Module subclass. I'm sure this approach can be backported as far as you need to go. On Sun, Nov 30, 2014 at 5:02 PM, Nathaniel Smith wrote: > On

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

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. What's left is preferences of core developers, possibly capabilities of the po

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 8:11 PM, Pierre-Yves David > wrote: > > > > On 11/30/2014 08:45 AM, Donald Stufft wrote: >> I don’t make branches in Mercurial because >> i’m afraid I’m going to push a permanent branch to hg.python.org >> and screw >> something up. > > There is n

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 04:31 AM, Paul Moore wrote: On 29 November 2014 at 23:27, Donald Stufft wrote: >In previous years there was concern about how well supported git was on Windows >in comparison to Mercurial. However git has grown to support Windows as a first >class citizen. In addition to that, f

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 08:45 AM, Donald Stufft wrote: I don’t make branches in Mercurial because i’m afraid I’m going to push a permanent branch to hg.python.org and screw something up. There is no need to be afraid there, Mercurial is not going to let you push new head/branch

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 04:31 AM, Paul Moore wrote: On 29 November 2014 at 23:27, Donald Stufft wrote: In previous years there was concern about how well supported git was on Windows in comparison to Mercurial. However git has grown to support Windows as a first class citizen. In addition to that, for

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Mon, Dec 1, 2014 at 12:59 AM, Nathaniel Smith wrote: > On Sun, Nov 30, 2014 at 10:14 PM, Mark Shannon wrote: >> Hi, >> >> This discussion has been going on for a while, but no one has questioned the >> basic premise. Does this needs any change to the language or interpreter? >> >> I believe it

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun, Nov 30, 2014 at 10:14 PM, Mark Shannon wrote: > Hi, > > This discussion has been going on for a while, but no one has questioned the > basic premise. Does this needs any change to the language or interpreter? > > I believe it does not. I'm modified your original metamodule.py to not use >

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 7:43 PM, Ben Finney wrote: > > Donald Stufft writes: > >> It’s not lost, [… a long, presumably-accurate discourse of the many >> conditions that must be met before …] you can restore it. > > This isn't the place to discuss the details of Git's internals, I think. > I'm m

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

Donald Stufft writes: > It’s not lost, [… a long, presumably-accurate discourse of the many > conditions that must be met before …] you can restore it. This isn't the place to discuss the details of Git's internals, I think. I'm merely pointing out that: > The important thing to realize is that

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 7:17 PM, Ben Finney wrote: > > Donald Stufft writes: > >> I have never heard of git losing history. > > In my experience talking with Git users about this problem, that depends > on a very narrow definition of “losing history”. > > Git encourages re-writing, and thereby

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

Donald Stufft writes: > I have never heard of git losing history. In my experience talking with Git users about this problem, that depends on a very narrow definition of “losing history”. Git encourages re-writing, and thereby losing prior versions of, the history of a branch. The commit inform

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On 11/30/2014 2:27 PM, Ethan Furman wrote: On 11/30/2014 11:15 AM, Guido van Rossum wrote: On Sun, Nov 30, 2014 at 6:15 AM, Brett Cannon wrote: On Sat, Nov 29, 2014, 21:55 Guido van Rossum wrote: All the use cases seem to be about adding some kind of getattr hook to modules. They all seem to

Re: [Python-Dev] Unicode decode exception

On 11/30/2014 3:07 AM, balaji marisetti wrote: Hi, When I try to iterate through the lines of a file("openssl-1.0.1j/crypto/bn/asm/x86_64-gcc.c"), I get a UnicodeDecodeError (in python 3.4.0 on Ubuntu 14.04). But there is no such error with python 2.7.6. What could be the problem? Questions ab

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 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. ... - I am basically the only remaining active PEP editor, so I see most PEP contributions by non-core-committers. Almost all of these uses github. Not bitbucket, not

Re: [Python-Dev] Unicode decode exception

Did you try opening it as a binary file? open(filename, 'rb'): — Tagada tsouin tsouin On Sun, Nov 30, 2014 at 5:06 PM, balaji marisetti wrote: > Hi, > When I try to iterate through the lines of a > file("openssl-1.0.1j/crypto/bn/asm/x86_64-gcc.c"), I get a > UnicodeDecodeError (in python

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, Nov 30, 2014 at 10:55 AM, Barry Warsaw wrote: > On Nov 30, 2014, at 09:54 AM, Ian Cordasco wrote: > > >- Migrating "data" from GitHub is easy. There are free-as-in-freedom > >tools to do it and the only cost is the time it would take to monitor > >the process > > *Extracting* data may be

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

Hi, This discussion has been going on for a while, but no one has questioned the basic premise. Does this needs any change to the language or interpreter? I believe it does not. I'm modified your original metamodule.py to not use ctypes and support reloading: https://gist.github.com/marksha

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 2:33 PM, Donald Stufft wrote: So a goal of mine here is to sort of use these as a bit of a test bed. Moving CPython itself is a big and drastic change with a lot of implications, but moving the “support” repositories is not nearly as much, especially with a read only mirror on hg.p

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 3:26 PM, Brett Cannon wrote: > > > > On Sun Nov 30 2014 at 2:33:35 PM Donald Stufft > wrote: > >> On Nov 30, 2014, at 2:19 PM, Brett Cannon > > wrote: >> >> All very true, but if we can't improve both sides then we are

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun, Nov 30, 2014 at 1:12 PM, Antoine Pitrou wrote: > On Sun, 30 Nov 2014 11:15:50 -0800 > Guido van Rossum wrote: > > On Sun, Nov 30, 2014 at 6:15 AM, Brett Cannon wrote: > > > > > > On Sat, Nov 29, 2014, 21:55 Guido van Rossum > wrote: > > > > > > All the use cases seem to be about addin

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun, 30 Nov 2014 11:15:50 -0800 Guido van Rossum wrote: > On Sun, Nov 30, 2014 at 6:15 AM, Brett Cannon wrote: > > > > On Sat, Nov 29, 2014, 21:55 Guido van Rossum wrote: > > > > All the use cases seem to be about adding some kind of getattr hook to > > modules. They all seem to involve modi

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 4:05 PM, Antoine Pitrou wrote: > > On Sun, 30 Nov 2014 10:05:01 -0800 > Guido van Rossum wrote: >> >> I bring this up to emphasize that (unlike GNU software and the FSF) Python >> has no additional hidden agenda of bringing freedom to all software. > > As far as GNU and

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun Nov 30 2014 at 3:55:39 PM Guido van Rossum wrote: > On Sun, Nov 30, 2014 at 11:29 AM, Nathaniel Smith wrote: > >> On Sun, Nov 30, 2014 at 2:54 AM, Guido van Rossum >> wrote: >> > All the use cases seem to be about adding some kind of getattr hook to >> > modules. They all seem to involve

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, 30 Nov 2014 10:05:01 -0800 Guido van Rossum wrote: > > I bring this up to emphasize that (unlike GNU software and the FSF) Python > has no additional hidden agenda of bringing freedom to all software. As far as GNU and the FSF are concerned, I don't think the agenda is "hidden" at all ;-

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, 30 Nov 2014 19:19:50 + Brett Cannon wrote: > > As the PEP points out, the devguide, devinabox, and the PEPs have such a > shallow development process that hosting them on Bitbucket wouldn't be a > big thing. But if we don't view this as a long-term step towards moving > cpython develo

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun, Nov 30, 2014 at 11:29 AM, Nathaniel Smith wrote: > On Sun, Nov 30, 2014 at 2:54 AM, Guido van Rossum > wrote: > > All the use cases seem to be about adding some kind of getattr hook to > > modules. They all seem to involve modifying the CPython C code anyway. So > > why not tackle that p

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 11:56 AM, Donald Stufft wrote: >> On Nov 30, 2014, at 2:28 PM, Ethan Furman wrote: >> >> My issues with GitHub range from selfish to philosophical: >> >> - (selfish) I don't want to learn git > > Note: That you don’t actually have to learn git, you can clone a git > repository > w

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun Nov 30 2014 at 2:33:35 PM Donald Stufft wrote: > > On Nov 30, 2014, at 2:19 PM, Brett Cannon wrote: > > All very true, but if we can't improve both sides then we are simply going > to end up with even more patches that we take a while to get around to. I > want to end up with a solution t

Re: [Python-Dev] Unicode decode exception

On Sun, Nov 30, 2014 at 7:07 PM, balaji marisetti wrote: > Hi, Hi. This list is for the development *of* Python, not development *with* Python, so I'm sending this reply also to python-l...@python.org where it can be better handled. You'll probably want to subscribe here: https://mail.python.org

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Mon, Dec 1, 2014 at 6:28 AM, Ethan Furman wrote: > My issues with GitHub range from selfish to philosophical: > > - (selfish) I don't want to learn git This ties in directly with the popularity argument. How many people are there who know hg and don't know git? How many who know git and don'

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 2:28 PM, Ethan Furman wrote: > > On 11/30/2014 10:05 AM, Guido van Rossum wrote: > >> Python has a long history (all the way back to my choice of a MIT-style >> license for the first release) of mixing "free" >> and "non-free" uses and tools -- for example on Windows we c

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun, Nov 30, 2014 at 7:27 PM, Ethan Furman wrote: > On 11/30/2014 11:15 AM, Guido van Rossum wrote: >> On Sun, Nov 30, 2014 at 6:15 AM, Brett Cannon wrote: >>> On Sat, Nov 29, 2014, 21:55 Guido van Rossum wrote: All the use cases seem to be about adding some kind of getattr hook

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun Nov 30 2014 at 2:28:31 PM Ethan Furman wrote: > On 11/30/2014 11:15 AM, Guido van Rossum wrote: > > On Sun, Nov 30, 2014 at 6:15 AM, Brett Cannon wrote: > >> On Sat, Nov 29, 2014, 21:55 Guido van Rossum wrote: > >>> > >>> All the use cases seem to be about adding some kind of getattr hook

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 2:19 PM, Brett Cannon wrote: > > All very true, but if we can't improve both sides then we are simply going to > end up with even more patches that we take a while to get around to. I want > to end up with a solution that advances the situation for *both* committers > an

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun, Nov 30, 2014 at 2:54 AM, Guido van Rossum wrote: > All the use cases seem to be about adding some kind of getattr hook to > modules. They all seem to involve modifying the CPython C code anyway. So > why not tackle that problem head-on and modify module_getattro() to look for > a global na

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun Nov 30 2014 at 2:16:18 PM Guido van Rossum wrote: > On Sun, Nov 30, 2014 at 6:15 AM, Brett Cannon wrote: >> >> On Sat, Nov 29, 2014, 21:55 Guido van Rossum wrote: >> >> All the use cases seem to be about adding some kind of getattr hook to >> modules. They all seem to involve modifying

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/30/2014 10:05 AM, Guido van Rossum wrote: > Python has a long history (all the way back to my choice of a MIT-style > license for the first release) of mixing "free" > and "non-free" uses and tools -- for example on Windows we consciously chose > to align ourselves with the platform > tool

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On 11/30/2014 11:15 AM, Guido van Rossum wrote: > On Sun, Nov 30, 2014 at 6:15 AM, Brett Cannon wrote: >> On Sat, Nov 29, 2014, 21:55 Guido van Rossum wrote: >>> >>> All the use cases seem to be about adding some kind of getattr hook >>> to modules. They all seem to involve modifying the CPython

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun Nov 30 2014 at 12:00:20 PM Donald Stufft wrote: > > On Nov 30, 2014, at 11:44 AM, Brett Cannon wrote: > > > > On Sun Nov 30 2014 at 10:55:26 AM Ian Cordasco > wrote: > >> On Sun, Nov 30, 2014 at 7:01 AM, Antoine Pitrou >> wrote: >> > On Sun, 30 Nov 2014 16:23:08 +1100 >> > Chris Angelic

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sun, Nov 30, 2014 at 6:15 AM, Brett Cannon wrote: > > On Sat, Nov 29, 2014, 21:55 Guido van Rossum wrote: > > All the use cases seem to be about adding some kind of getattr hook to > modules. They all seem to involve modifying the CPython C code anyway. So > why not tackle that problem head-o

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> 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? This is probably an issue we’re never going to get actual consens

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

Can this discussion be split off into a separate discussion. It's tangential to the PEP and clearly not actively progressing so it doesn't seem productive. I don't care where it's taken, but I don't think this belongs here. Speculation on the actions of the msysgit project are not fair talk for thi

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 30 November 2014 at 16:08, Donald Stufft wrote: >> On Nov 30, 2014, at 7:31 AM, Paul Moore wrote: >> >> On 29 November 2014 at 23:27, Donald Stufft wrote: >>> In previous years there was concern about how well supported git was on >>> Windows >>> in comparison to Mercurial. However git has g

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

I don't feel it's my job to accept or reject this PEP, but I do have an opinion. The scope of the PSF organization is far beyond just the Python language -- it includes the Python developer community, the Python user community, 3rd party Python packages and their communities (even if some have cre

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 11:17, Chris Angelico wrote: > > On Sun, Nov 30, 2014 at 8:54 PM, Nick Coghlan wrote: >> On 30 November 2014 at 15:23, Chris Angelico wrote: >>> Python is already using quite a bit of non-free software in its >>> ecosystem. The Windows builds of CPython are made with Micr

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 11/29/2014 10:14 PM, Demian Brecht wrote: > > On Sat, Nov 29, 2014 at 3:27 PM, Donald Stufft > wrote: >> As promised in the "Move selected documentation repos to PSF BitBucket >> account?" thread I've written up a PEP for moving selected repositories from >> hg.python.

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 11:30 AM, Donald Stufft wrote: > > Comments like this make me feel like I didn’t explain myself very well in the > PEP. It’s been pointed out to me that Mercurial bookmarks have been core since 1.8 and since I felt like the technical arguments were really secondary to the

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Nov 30, 2014 11:09 AM, "Donald Stufft" wrote: > > > > On Nov 30, 2014, at 11:55 AM, Barry Warsaw wrote: > > > > On Nov 30, 2014, at 09:54 AM, Ian Cordasco wrote: > > > >> - Migrating "data" from GitHub is easy. There are free-as-in-freedom > >> tools to do it and the only cost is the time it w

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 12:09 PM, Donald Stufft wrote: > >> >> On Nov 30, 2014, at 11:55 AM, Barry Warsaw wrote: >> >> On Nov 30, 2014, at 09:54 AM, Ian Cordasco wrote: >> >>> - Migrating "data" from GitHub is easy. There are free-as-in-freedom >>> tools to do it and the only cost is the time

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 11:55 AM, Barry Warsaw wrote: > > On Nov 30, 2014, at 09:54 AM, Ian Cordasco wrote: > >> - Migrating "data" from GitHub is easy. There are free-as-in-freedom >> tools to do it and the only cost is the time it would take to monitor >> the process > > *Extracting* data may

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 11:44 AM, Brett Cannon wrote: > > > > On Sun Nov 30 2014 at 10:55:26 AM Ian Cordasco > wrote: > On Sun, Nov 30, 2014 at 7:01 AM, Antoine Pitrou > wrote: > > On Sun, 30 Nov 2014 16:23:08 +1100 > > Chris Angel

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Nov 30, 2014, at 09:54 AM, Ian Cordasco wrote: >- Migrating "data" from GitHub is easy. There are free-as-in-freedom >tools to do it and the only cost is the time it would take to monitor >the process *Extracting* data may be easy, but migrating it is a different story. As the Mailman project

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, Nov 30, 2014, at 11:45, Donald Stufft wrote: > > > On Nov 30, 2014, at 11:28 AM, Brett Cannon wrote: > > > > > > > > On Sat Nov 29 2014 at 7:16:34 PM Alex Gaynor > > wrote: > > Donald Stufft stufft.io > writes: > > > > > > > > [word

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun Nov 30 2014 at 10:55:26 AM Ian Cordasco wrote: > On Sun, Nov 30, 2014 at 7:01 AM, Antoine Pitrou > wrote: > > On Sun, 30 Nov 2014 16:23:08 +1100 > > Chris Angelico wrote: > >> > >> Yes, GitHub is proprietary. But all of your actual code is stored in > >> git, which is free, and it's easy

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 11:28 AM, Brett Cannon wrote: > > > > On Sat Nov 29 2014 at 7:16:34 PM Alex Gaynor > wrote: > Donald Stufft stufft.io > writes: > > > > > [words words words] > > > > I strongly support this PEP. I'd like to share two pi

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun Nov 30 2014 at 10:28:50 AM Brett Cannon wrote: > Why specifically? Did you have a web UI for reviewing patches previously? > Do you have CI set up for patches now and didn't before? What features did > you specifically gain from the switch to GitHub that you didn't have > before? IOW was i

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 6:18 AM, 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 >>

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 2:08 AM, Larry Hastings wrote: > > > On 11/29/2014 04:37 PM, Donald Stufft wrote: >> On Nov 29, 2014, at 7:15 PM, Alex Gaynor >> wrote: >>> Despite being a regular hg >>> user for years, I have no idea how to create a local-only branch, or

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sat Nov 29 2014 at 7:16:34 PM Alex Gaynor wrote: > Donald Stufft stufft.io> writes: > > > > > [words words words] > > > > I strongly support this PEP. I'd like to share two pieces of information. > Both > of these are personal anecdotes: > > For the past several years, I've been a contributor

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

> On Nov 30, 2014, at 7:31 AM, Paul Moore wrote: > > On 29 November 2014 at 23:27, Donald Stufft wrote: >> In previous years there was concern about how well supported git was on >> Windows >> in comparison to Mercurial. However git has grown to support Windows as a >> first >> class citizen.

[Python-Dev] Unicode decode exception

Hi, When I try to iterate through the lines of a file("openssl-1.0.1j/crypto/bn/asm/x86_64-gcc.c"), I get a UnicodeDecodeError (in python 3.4.0 on Ubuntu 14.04). But there is no such error with python 2.7.6. What could be the problem? In [39]: with open("openssl-1.0.1j/crypto/bn/asm/x86_64-gcc.c"

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

- [ ] Paste-able links On Sun, Nov 30, 2014 at 12:31 AM, Wes Turner wrote: > - [ ] Stable URIs > - [ ] Commit hashes > > On Sun, Nov 30, 2014 at 12:11 AM, Wes Turner wrote: > >> - [ ] Markdown >> - [ ] ReStructuredText >> >> - [ ] Review (why are these out of band?) >> >> On Sat, Nov 29, 2014 a

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

https://kallithea-scm.org/repos/kallithea/files/tip/setup.py https://github.com/codeinn/vcs/blob/master/setup.py On Sun, Nov 30, 2014 at 1:16 AM, Wes Turner wrote: > Is there a kalithea celery task to mirror / SYNC with github, for pull > requests and/or issues? > > https://pypi.python.org/pyp

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

Is there a kalithea celery task to mirror / SYNC with github, for pull requests and/or issues? https://pypi.python.org/pypi/Kallithea/ https://kallithea-scm.org/ https://kallithea-scm.org/repos/kallithea https://bitbucket.org/conservancy/kallithea http://pythonhosted.org//Kallithea http://kallith

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

- [ ] Stable URIs - [ ] Commit hashes On Sun, Nov 30, 2014 at 12:11 AM, Wes Turner wrote: > - [ ] Markdown > - [ ] ReStructuredText > > - [ ] Review (why are these out of band?) > > On Sat, Nov 29, 2014 at 11:34 PM, Wes Turner wrote: > >> Specifically, which features are most ideal here? >> >>

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

- [ ] Markdown - [ ] ReStructuredText - [ ] Review (why are these out of band?) On Sat, Nov 29, 2014 at 11:34 PM, Wes Turner wrote: > Specifically, which features are most ideal here? > > - [ ] Userbase > - [ ] TTW editing only over SSL (see: Zope 2) > - [ ] Pull Requests (see also: BitBucket,

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

Larry Hastings writes: > On 11/29/2014 04:37 PM, Donald Stufft wrote: >> On Nov 29, 2014, at 7:15 PM, Alex Gaynor wrote: >>> Despite being a regular hg >>> user for years, I have no idea how to create a local-only branch, or a >>> branch >>> which is pushed to a remote (to use the git term). >>

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, Nov 30, 2014 at 7:01 AM, Antoine Pitrou wrote: > On Sun, 30 Nov 2014 16:23:08 +1100 > Chris Angelico wrote: >> >> Yes, GitHub is proprietary. But all of your actual code is stored in >> git, which is free, and it's easy to push that to a new host somewhere >> else, or create your own host

Re: [Python-Dev] advice needed: best approach to enabling "metamodules"?

On Sat, Nov 29, 2014, 21:55 Guido van Rossum wrote: All the use cases seem to be about adding some kind of getattr hook to modules. They all seem to involve modifying the CPython C code anyway. So why not tackle that problem head-on and modify module_getattro() to look for a global named __getat

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, 30 Nov 2014 16:23:08 +1100 Chris Angelico wrote: > > Yes, GitHub is proprietary. But all of your actual code is stored in > git, which is free, and it's easy to push that to a new host somewhere > else, or create your own host. This proposal is for repositories that > don't need much in t

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On 29 November 2014 at 23:27, Donald Stufft wrote: > In previous years there was concern about how well supported git was on > Windows > in comparison to Mercurial. However git has grown to support Windows as a > first > class citizen. In addition to that, for Windows users who are not well > a

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

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. GitHub deliberately encourages proprietary features

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

Chris Angelico writes: > But what non-free software is required to use the community design > processes? The GitHub client is entirely optional; I don't use it, I > just use git itself. Using a free client to access a proprietary > server isn't the same as using non-free software. For that to re

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

I have some questions and/or issues with the PEP, but first I'm going to add something to Nick's comments: On Sun, Nov 30, 2014 at 11:12:17AM +1000, Nick Coghlan wrote: > Beyond that, GitHub is indeed the most expedient option. My two main > reasons for objecting to taking the expedient path are

Re: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

On Sun, Nov 30, 2014 at 8:54 PM, Nick Coghlan wrote: > On 30 November 2014 at 15:23, Chris Angelico wrote: >> Python is already using quite a bit of non-free software in its >> ecosystem. The Windows builds of CPython are made with Microsoft's >> compiler, and the recent discussion about shifting

  1   2   >