On 30 June 2013 05:08, Ethan Furman wrote:
> I was hoping to provide good examples of Python 3 code (as opposed to good
> examples of 2/3 boundary straddling), but yeah, it's danged difficult!
Writing idiomatic Python 3 code and supporting both Python 2 & 3
aren't really compatible goals. I sugge
On 06/29/2013 02:07 AM, Nick Coghlan wrote:
On 29 June 2013 10:09, Ethan Furman wrote:
Am I making this too complicated? Can I just do my renaming in the setup.py
script before calling the setup function?
You can't easily create a wheel that way.
What would actually be better is if you coul
On 29 June 2013 10:09, Ethan Furman wrote:
> Am I making this too complicated? Can I just do my renaming in the setup.py
> script before calling the setup function?
You can't easily create a wheel that way.
What would actually be better is if you could avoid the need for any
Python 3 specific s
On 06/27/2013 11:55 AM, Oscar Benjamin wrote:
On 27 June 2013 18:31, Ethan Furman wrote:
It occur to me now that the reason I don't see this kind of error on
my project is because in the setup.py I am just excluding the
version-specific files based on what Python version the user has.
Perhaps
On 06/28/2013 04:45 PM, Ethan Furman wrote:
On 06/27/2013 11:55 AM, Oscar Benjamin wrote:
On 27 June 2013 18:31, Ethan Furman wrote:
It occur to me now that the reason I don't see this kind of error on
my project is because in the setup.py I am just excluding the
version-specific files based
On 27 June 2013 18:31, Ethan Furman wrote:
>>
>> It occur to me now that the reason I don't see this kind of error on
>> my project is because in the setup.py I am just excluding the
>> version-specific files based on what Python version the user has.
>> Perhaps you should do the same--only instal
Le 26/06/2013 17:19, Ethan Furman a écrit :
> Is there an option to tell distutils not to compile byte code?
Yes. setup.py build --help should show you the options, otherwise see
http://hg.python.org/cpython/file/dad02a080bbc/Doc/packaging/commandref.rst#l113
(I should backport that doc change to
On 06/27/2013 10:19 AM, Erik Bray wrote:
On Wed, Jun 26, 2013 at 4:21 PM, Erik Bray wrote:
On Sun, Jun 16, 2013 at 3:13 AM, Ethan Furman wrote:
Here's my file layout:
/
|- setup.py
|
|- enum /
|- __init__.py
|
|- py2_en
On Wed, Jun 26, 2013 at 4:21 PM, Erik Bray wrote:
> On Sun, Jun 16, 2013 at 3:13 AM, Ethan Furman wrote:
>> Here's my file layout:
>>
>> /
>>|- setup.py
>>|
>>|- enum /
>>|- __init__.py
>>|
>>|- py2_enum.py
>>
On 06/26/2013 01:35 PM, Carl Meyer wrote:
On 06/26/2013 02:23 PM, Donald Stufft wrote:
If I recall this is because it's trying to compile byte code.
That's correct. And you'll note that despite the scary-looking syntax
errors from byte-compilation, the install actually succeeded.
I did noti
On 06/26/2013 01:23 PM, Donald Stufft wrote:
If I recall this is because it's trying to compile byte code.
Is there an option to tell distutils not to compile byte code?
--
~Ethan~
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.
On 06/26/2013 01:21 PM, Erik Bray wrote:
On Sun, Jun 16, 2013 at 3:13 AM, Ethan Furman wrote:
Here's my file layout:
/
|- setup.py
|
|- enum /
|- __init__.py
|
|- py2_enum.py
|
|- py3_enum.
On 06/26/2013 02:23 PM, Donald Stufft wrote:
>
> On Jun 26, 2013, at 4:21 PM, Erik Bray wrote:
>
>> On Sun, Jun 16, 2013 at 3:13 AM, Ethan Furman wrote:
>>> Here's my file layout:
>>>
>>> /
>>> |- setup.py
>>> |
>>> |- enum /
>>> |- __init__.py
>>>
On Jun 26, 2013, at 4:21 PM, Erik Bray wrote:
> On Sun, Jun 16, 2013 at 3:13 AM, Ethan Furman wrote:
>> Here's my file layout:
>>
>> /
>> |- setup.py
>> |
>> |- enum /
>> |- __init__.py
>> |
>> |- py2_enum.py
>> |
>>
On Sun, Jun 16, 2013 at 3:13 AM, Ethan Furman wrote:
> Here's my file layout:
>
> /
>|- setup.py
>|
>|- enum /
>|- __init__.py
>|
>|- py2_enum.py
>|
>|- py3_enum.py
>|
>
Here's my file layout:
/
|- setup.py
|
|- enum /
|- __init__.py
|
|- py2_enum.py
|
|- py3_enum.py
|
|- test /
|- test_enum.py
16 matches
Mail list logo
