On Sun, Dec 9, 2012 at 3:48 PM, PJ Eby wrote:
> That's why I keep asking for specific, concrete use cases. At this
> point, for the field to make any sense, there needs to be some better
> idea of what a "runtime" or "undefined" conflict is. Apart from file
> conflicts, has anybody identified a
On Sun, Dec 9, 2012 at 6:18 AM, PJ Eby wrote:
> On Sat, Dec 8, 2012 at 5:06 AM, Nick Coghlan wrote:
> > On Sat, Dec 8, 2012 at 4:46 PM, PJ Eby wrote:
> >>
> >> So if package A includes a "Conflicts: B" declaration, I recommend the
> >> following:
> >>
> >> * An attempt to install A with B alrea
On Sat, Dec 8, 2012 at 10:22 PM, MRAB wrote:
> On 2012-12-09 01:15, Steven D'Aprano wrote:
>>
>> On 09/12/12 08:14, MRAB wrote:
>>
>>> If package A says that it conflicts with package B, it may or may not
>>> be symmetrical, because it's possible that package B has been updated
>>> since the autho
On Sun, Dec 9, 2012 at 8:41 AM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/08/2012 05:06 AM, Nick Coghlan wrote:
>
> > Building integrated systems *is hard*. Pretending projects can't
> > conflict just because they're both written in Python isn't sensible,
> >
On Dec 8, 2012, at 8:37 PM, Gregory P. Smith wrote:
> Is twisted's spawnProcess thread safe and async signal safe by using
> restricted C code for everything between the fork() and exec()? I'm not
> familiar enough with the twisted codebase to find things easily in it but I'm
> not seeing su
On Sat, Dec 8, 2012 at 8:14 PM, Glyph wrote:
>
> On Dec 7, 2012, at 5:10 PM, anatoly techtonik wrote:
>
> What about reading from other file descriptors? subprocess.Popen allows
>> arbitrary file descriptors to be used. Is there any provision here for
>> reading and writing non-blocking from o
I'm really not sure what this PEP is trying to get at given that it
contains no examples and sounds from the descriptions to be adding a
complicated api on top of something that already, IMNSHO, has too much it
(subprocess.Popen).
Regardless, any user can use the stdout/err/in file objects with th
On Dec 7, 2012, at 5:10 PM, anatoly techtonik wrote:
> What about reading from other file descriptors? subprocess.Popen allows
> arbitrary file descriptors to be used. Is there any provision here for
> reading and writing non-blocking from or to those?
>
> On Windows it is WriteFile/ReadFil
On Sat, Dec 08, 2012 at 01:07:43PM -0800, A G wrote:
> Ideally I'd like to resolve these and submit a port for python3.3 since
> the most recent FreeBSD port is stuck on 3.2.
FWIW, the FreeBSD Python port maintainer, Kubilay Kocak, is active
on #python-dev@freenode under the nick 'koobs'.
On 2012-12-09 01:15, Steven D'Aprano wrote:
On 09/12/12 08:14, MRAB wrote:
If package A says that it conflicts with package B, it may or may not
be symmetrical, because it's possible that package B has been updated
since the author of package A discovered the conflict, so it's
important that th
On Sun, Dec 9, 2012 at 1:11 PM, Steven D'Aprano wrote:
> On 09/12/12 12:32, Chris Angelico wrote:
>>
>> On Sun, Dec 9, 2012 at 12:15 PM, Steven D'Aprano
>> wrote:
>>>
>>> Assuming that two software packages Spam and Ham install into directories
>>> Spam and Ham, how can merely having them installe
On Saturday, December 8, 2012 at 9:11 PM, Steven D'Aprano wrote:
> Why would a software package called "Spam" install a top-level module called
> "Jam" rather than "Spam"? Isn't the whole point of Python packages to solve
> this namespace problem?
>
Conflicts doesn't really solve file based confli
On 09/12/12 12:32, Chris Angelico wrote:
On Sun, Dec 9, 2012 at 12:15 PM, Steven D'Aprano wrote:
Assuming that two software packages Spam and Ham install into directories
Spam and Ham, how can merely having them installed side-by-side lead to a
conflict?
I can see how running or importing Spam
On Sun, Dec 9, 2012 at 12:15 PM, Steven D'Aprano wrote:
> Assuming that two software packages Spam and Ham install into directories
> Spam and Ham, how can merely having them installed side-by-side lead to a
> conflict?
>
> I can see how running or importing Spam and Ham together might lead to
> p
On 09/12/12 08:14, MRAB wrote:
If package A says that it conflicts with package B, it may or may not
be symmetrical, because it's possible that package B has been updated
since the author of package A discovered the conflict, so it's
important that the user is told which package is complaining a
A G wrote:
> ==
> FAIL: test_saltedcrypt (test.test_crypt.CryptTestCase)
> --
> Traceback (most recent call last):
> File "/usr/home/adam/Python-3.3.0/Lib/test/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/08/2012 05:06 AM, Nick Coghlan wrote:
> Building integrated systems *is hard*. Pretending projects can't
> conflict just because they're both written in Python isn't sensible,
> and neither is it sensible to avoid warning users about the the
> p
Hark fellow Emacsers. All you unenlightened heathens can stop reading now.
A few years ago, my colleague Jono Lange wrote probably the best little chunk
of Emacs lisp ever. `M-x bzr-tools-grep` lets you easily search a Bazaar
repository for a case-sensitive string, providing you with a nice *gre
On 2012-12-08 20:18, PJ Eby wrote:
On Sat, Dec 8, 2012 at 5:06 AM, Nick Coghlan wrote:
On Sat, Dec 8, 2012 at 4:46 PM, PJ Eby wrote:
So if package A includes a "Conflicts: B" declaration, I recommend the
following:
* An attempt to install A with B already present refuses to install A
withou
Hello All,
I am successfully compiling python 3.3 on FreeBSD 9.0 amd64 architecture.
When I run the tests, I get these two test failures ( I trimmed out all the
output from test cases that returned ok):
test_saltedcrypt (test.test_crypt.CryptTestCase) ... FAIL
==
On Sat, Dec 8, 2012 at 5:06 AM, Nick Coghlan wrote:
> On Sat, Dec 8, 2012 at 4:46 PM, PJ Eby wrote:
>>
>> So if package A includes a "Conflicts: B" declaration, I recommend the
>> following:
>>
>> * An attempt to install A with B already present refuses to install A
>> without a warning and confi
On Sat, Dec 8, 2012 at 4:46 PM, PJ Eby wrote:
> So if package A includes a "Conflicts: B" declaration, I recommend the
> following:
>
> * An attempt to install A with B already present refuses to install A
> without a warning and confirmation
> * An attempt to install B informs the user of the co
22 matches
Mail list logo
